For Alaska Part 135 operators, air taxis & charter services
Charter quotes, load manifests, maintenance records, duty time, and weather cancellations all generate paperwork that has to be right. We build agents that handle the repetitive parts without ever touching an airworthiness or a go/no-go decision.
Built in Anchorage · we publish our source code · no long-term lock-in
Written by Kristian Baer, Northtek · Anchorage, Alaska · Updated 2026-08-21
The short answer
The administrative half of the operation, and nothing that touches safety of flight. Charter quoting, manifest preparation, passenger and cargo communication, maintenance document tracking, and records search are all repetitive, rule-bound, and consume dispatcher and director-of-operations hours. Airworthiness determinations, go/no-go calls, weight and balance sign-off, and duty time decisions stay with the certificated people who own them, full stop. We build the first list and we refuse the second, and we put that boundary in the scope document so there is no ambiguity later.
The operating reality
Many communities have no other year-round access. That makes small operators critical infrastructure with a regulatory burden sized for much larger companies.
A weather day cascades into rebooking, cargo reprioritization, and dozens of customer conversations. The flying decision is the captain’s. The forty phone calls afterward are not a good use of a dispatcher.
A six-aircraft operator carries recordkeeping obligations comparable in kind to a much larger carrier, with a fraction of the administrative staff to satisfy them.
Mixed loads mean manifest and weight documentation changes right up to departure, and the last-minute version is the one that has to be correct and retained.
Your customers are the same people every week. Communication that sounds automated damages a relationship that took years to build, so anything customer-facing gets reviewed by a person before it sends.
Six workflows we build
All of them administrative. None of them anywhere near an airworthiness or a dispatch release decision.
01
02
03
04
05
06
First 30 days
A weather day already costs you the revenue. It should not also cost your dispatcher six hours and your customers their patience.
We reconstruct one recent disruption call by call and count the communication time and what fell through. That is the baseline, taken from your operation rather than an industry average.
It drafts personalized messages with real rebooking options in your operation’s voice. Nothing sends without a dispatcher approving the batch, because these are your neighbors.
Live, with your dispatcher in control, on a real disruption. We measure communication time and complaints against the baseline.
What you own at day 30
A disruption communication agent wired to your booking records, a measured comparison against a real prior weather day, the source code and configuration, and a written scope document stating explicitly which decisions the system will never make.
What we built, in the open
Any vendor will tell you their tool stays clear of safety of flight. The question is whether the system is built so it cannot drift there as features get added. Owning the agent language is what lets us define that boundary in code and hand your director of operations something they can point an inspector at.
A language and compiler we wrote so an agent's permitted actions are explicit and its steps are auditable. The scope limit is a property of the system rather than a promise in a proposal.
Verification between the model and your records, so a component time or compliance date read off a work order is checked against the source rather than trusted.
Our own memory server. It is why records search and manual retrieval can run inside your environment, which matters when the corpus is your operations manual and your training files.
All public with commit history. For an operation that gets audited, a vendor whose engineering can be inspected is a different proposition than one whose cannot.
Scope, stated up front
The line between administrative work and safety of flight is the whole design. Three things that stay on the other side of it.
It never touches safety of flight
No go/no-go input, no weight and balance approval, no airworthiness determination, no duty time decision. Those belong to certificated people and we will decline the scope if asked.
It is not an FAA compliance product
We build workflow tools that keep your documents organized and searchable. They are not certified, they are not a substitute for your compliance program, and we do not describe them that way.
Customer messages get reviewed
In village service the relationship is the business. Every customer-facing message is approved by a person before it sends, by design, and we do not offer a fully autonomous mode.
Where your data goes
Records are the regulated asset here, and communication is the relationship. Five commitments we put in the agreement.
It touches documents, never decisions. Maintenance records get organized and deadlines get flagged; your director of maintenance still makes every airworthiness call. Manifests get assembled; the crew still performs and signs weight and balance. We write that boundary into the scope document so there is no ambiguity during an audit.
Small operators are usually the better fit, because the recordkeeping burden does not shrink with the fleet but the administrative staff does. A one-person dispatch office feels the gain immediately.
We integrate with what you run - FlightLogger, a maintenance tracking system, a booking platform, or a set of spreadsheets that works. If your system has no integration point, we work through the interface a person would use rather than asking you to replace it.
The administrative side works the same way, with a stricter boundary: anything involving patient information requires a signed business associate agreement and infrastructure you control before we build. See the healthcare playbook for how we handle protected health information.
Only if you let it. Every customer-facing message is drafted, then approved by your dispatcher before it sends. The gain is that they approve forty messages in ten minutes instead of making forty phone calls, and each message still says the right thing to the right person.
Yes. The quoting piece matters less, but records search, maintenance document tracking, and audit response are the same problems with the same solution.
We will show you which parts of it a person had to do and which parts were just typing. Sixty minutes, no cost, honest answer at the end.
Anchorage, Alaska · info@northtek.io · (907) 903-4353