American Airlines flight AAL9788, operating an Airbus A320 on a PAE-to-PAE routing with a touch-and-go at Seattle-Tacoma International Airport (SEA), is characteristic of a non-revenue special operations flight — most likely a maintenance functional check flight (FCF) or a crew training/proficiency sortie. The 9000-series flight number is the clearest indicator: major U.S. carriers, including American, reserve high-block flight numbers (typically 9000–9999) for ferry flights, positioning moves, maintenance check flights, and training operations that do not carry revenue passengers. These flights are still operated under the carrier's FAA certificate and appear on tracking platforms like FlightAware with full transponder data, which is why the routing looked legitimate but operationally unusual to an observer.
The PAE origin and destination, combined with the SEA touch-and-go, narrows the likely explanation further. Paine Field serves as a convenient staging point for special operations in the Pacific Northwest — it is less congested than SEA and has long been associated with aircraft maintenance, modification, and delivery activity. While PAE is historically tied to Boeing widebody deliveries, it also hosts MRO (maintenance, repair, and overhaul) activity for various aircraft types. An A320 undergoing maintenance work at or near the Everett area could legitimately stage out of PAE for a functional check flight, with the SEA touch-and-go serving as a controlled-environment systems verification under realistic approach and landing conditions before the aircraft is returned to revenue service. Alternatively, the flight could represent a crew qualification or recurrency event, with line check airmen or training captains using the PAE-SEA corridor for approach and landing currency in a lower-pressure environment than a full scheduled operation.
For working pilots and aviation operators, this type of flight illustrates how major carriers conduct the unglamorous but operationally critical back-end work that keeps certificated fleets airworthy and crews current. Part 121 operators are required to conduct functional check flights following certain categories of maintenance, and those flights must be staffed by qualified crews flying under the carrier's OpSpecs. Similarly, simulator-based training programs are periodically supplemented by aircraft events — particularly for procedures or environmental conditions that full-flight simulators do not replicate with sufficient fidelity. The fact that the flight appeared on FlightAware with a standard ICAO callsign reflects that it was filed and operated under IFR with ATC coordination, as would be expected for any flight into the Class B airspace surrounding SEA.
The broader context here touches on how airline operations are increasingly visible to the public through ADS-B tracking, which creates a steady stream of "unusual flight" observations from aviation enthusiasts who correctly notice deviations from expected patterns. For professional pilots and operators, it is worth understanding that 9XXX-series and other high-block flight numbers are a universal shorthand across most major carriers for non-passenger special operations — a convention that Part 135 and corporate operators sometimes mirror with their own internal numbering schemes for ferry, positioning, and check flights. Recognizing these conventions helps differentiate genuinely anomalous operations from routine but opaque airline housekeeping, and reinforces that even a seemingly odd routing from PAE to PAE almost always has a straightforward regulatory or operational rationale behind it.