LIVE · BRIEFING WIRE
FlightLogic Brief Daily aviation wire
← Google News
● GN AGGR ·February 21, 2026 ·08:00Z

FAA Part 135 private jet charter list contains many mistakes - Private Jet Card Comparisons

FAA Part 135 private jet charter list contains many mistakes Private Jet Card Comparisons [truncated: Google News RSS provides only a snippet, not full article
Detailed analysis

The FAA's publicly available Part 135 Operators and Aircraft List, designed to help consumers verify the legitimacy of charter operators before booking a flight, has been found to contain pervasive data errors that render it unreliable for its intended purpose. Documented discrepancies include aircraft listed under technical designation codes rather than common names — "EMB-505" in place of "Phenom 300," or "CE-680" instead of "Citation Latitude" — creating confusion for anyone without deep familiarity with FAA type certification terminology. More critically, over 21,000 of the list's approximately 23,000 aircraft entries were incorrectly attributed to Southern Seaplane, a single Louisiana-based operator, rather than to the actual certificated carriers operating those aircraft, including major fleet operators like NetJets. Aircraft belonging to defunct operators also remain on the list, while some actively chartered jets are absent entirely. The FAA issued multiple revisions in February 2026, but errors persisted through each update cycle.

The practical stakes for the charter industry are considerable. Part 135 certification is the regulatory backbone of on-demand commercial air transportation in the United States, and the public-facing operator list exists specifically so that consumers — and their corporate travel managers — can cross-reference tail numbers before purchasing charter services. Illegal charter, in which operators conduct revenue flights without proper certification, remains an ongoing enforcement concern for the FAA. When the verification tool itself is corrupted by data inconsistencies, the consumer protection rationale for publishing it collapses. The FAA responded by announcing plans to deactivate the list entirely until it can be validated and made current, with integration into AVinfo.gov cited as the longer-term solution for improved data management and accuracy.

For Part 135 operators, the situation exposes a structural vulnerability in how the FAA maintains and publishes certification records at scale. The industry is fragmented by design — approximately 87 percent of Part 135 operators hold fewer than 10 certificated aircraft — but large fractional and charter fleet operators with hundreds of tail numbers depend on accurate public records for operator legitimacy signaling to clients. A list that incorrectly aggregates more than 21,000 aircraft under a single unrelated carrier does not merely inconvenience consumers; it actively undermines the credibility of operators with spotless safety records and current certificates. For flight departments operating under Part 91K or using Part 135 carriers for supplemental lift, the inability to quickly verify an unfamiliar operator through official FAA channels shifts the due diligence burden entirely onto the buyer.

The episode also reflects a broader tension within FAA data infrastructure as the agency manages increasingly large and complex certification datasets across aging systems. The announced migration to AVinfo.gov suggests the FAA recognizes the long-term inadequacy of maintaining siloed, manually updated public lists. However, the decision to deactivate the existing list before a functional replacement is operational leaves a temporary gap in publicly accessible operator verification — precisely the kind of ambiguity that bad actors in the illegal charter market are known to exploit. Professional pilots operating in the charter and fractional space, as well as the corporate flight departments that rely on Part 135 carriers for trip support, should ensure their vendor vetting processes do not depend solely on the FAA's public list and instead incorporate direct certificate verification through FSDO contacts or dedicated charter audit services until AVinfo.gov integration is confirmed operational and accurate.

Read original article