The airplane is parked at TEB, or HPN, or a field two hours from anywhere, and it is not moving. The passengers are rebooking, and the clock started before anyone picked up a phone. When an aircraft goes AOG, the first hour usually decides whether you are flying tonight or explaining tomorrow.
We answer that first call for operators across the Northeast, so here is what the hour looks like when it goes well, from the dispatch side of the phone.
Capture the squawk before you make the call
The instinct is to start dialing. Resist it for ten minutes. Have the crew write down exactly what happened: the fault message or CAS text word for word (a photo of the display beats a paraphrase), when it appeared, what the crew was doing at the time, and anything they already tried. Add where the aircraft is parked and who controls access to that ramp.
A precise discrepancy report shortens everything that follows. A vague one means the technician spends the first hour on site troubleshooting the report instead of the aircraft. Ten minutes of capture on the front end regularly saves hours on the back end.
One good call, then a work authorization
A mobile maintenance provider needs four things to say yes: the aircraft type, where it is, the discrepancy as the crew captured it, and when you need it flying. With those in hand, remote triage starts immediately: narrowing the likely system, thinking through parts, and deciding whether this is a single-technician dispatch or a two-technician job.
Then comes the document that keeps the rest of the day honest: the work authorization. Nothing starts before you approve it. Scope, approach, and approval in plain language, so the maintenance bill is one you signed off on, not one that happened to you. Transparent, authorization-driven service means no surprise invoices, and it starts in this hour, not at the end of the job.
What is rolling toward you
Once you authorize, dispatch is in motion: a mobile-equipped FAA-certified A&P technician, travel coordination, and the parts thinking that started during triage. Complex or multi-system squawks get a two-technician team.
This is the part of the hour you cannot see, so ask your provider to narrate it. We hold ourselves to sub-2-hour AOG response and 24/7/365 availability, and a good dispatcher will tell you who is coming, from where, and what they are bringing, while it is happening.
On the ramp: troubleshoot, update, release
On arrival the work is fault isolation, not guesswork: confirm the discrepancy, trace it to a system or component, and fix what the authorization covers. If the scope changes, the change comes back through you before more work happens.
Release is paperwork done right: operational and leak checks, an FAA-compliant logbook entry, parts traceability, and 8130 documentation. Audit-ready paperwork on the spot, before the aircraft flies, not mailed later.
Make the next one a five-minute call
The operators who lose the least time to AOG events did their first hour in advance. The provider already knows their aircraft, their fields, who can authorize work, and how they like updates. When something breaks, the call takes five minutes because everything else is already on file.
If you would rather have that conversation on a calm afternoon than a jammed ramp, start with a service request and tell us about your aircraft. We are around 24/7/365, and we would rather meet you before the clock is running.