The phrase "I've got a number for you to call" is one of the more quietly unsettling transmissions a pilot can hear from Air Traffic Control, and its appearance as a discussion topic on aviation forums reflects genuine uncertainty among pilots about what the phrase actually triggers procedurally. In practice, this language is ATC's way of flagging a possible pilot deviation (PD) without immediately escalating the situation over the radio. Rather than confronting a pilot mid-flight about a suspected altitude bust, course deviation, runway incursion, or readback error, the controller notes the event, and at some point—often near the end of the flight or after handoff to the next sector—relays a phone number, typically for the local FAA Flight Standards District Office (FSDO) or the TRACON/Tower Watch Supervisor, for the pilot to call after landing.
Procedurally, the call is not technically "mandatory" in the sense that ATC cannot force a pilot to dial the phone, but declining to call does not make the underlying issue disappear. Once a controller identifies a potential deviation, they are generally required to notify their supervisor and initiate a preliminary PD report, which can trigger a Brasher Notification (informing the pilot, on frequency, that a possible pilot deviation occurred and that a phone number will be provided). If the pilot never calls, the FAA can still proceed with an investigation using ATC tapes, radar data, and the controller's report alone, but the pilot loses the opportunity to provide immediate context, mitigating information, or corrections to the record. Many aviation attorneys and experienced pilots strongly advise making the call, but doing so carefully: acknowledging the request politely, keeping any conversation brief and factual, and in more serious cases, consulting with an aviation attorney or AOPA/NBAA legal services plan before providing detailed statements, since anything said can factor into subsequent 709 rides, certificate actions, or Aviation Safety Reporting System (ASRS) considerations.
For working pilots—airline, Part 91/135, and business aviation crews alike—this topic matters because it sits at the intersection of professional judgment, regulatory exposure, and crew resource management. A single readback error, a missed altitude restriction, or a runway hold-short violation can result in this phone number request, and how a pilot and their operator handle the aftermath has real career implications, particularly for airline pilots whose unions provide structured guidance and for Part 135/91K operators where a single pilot may face the FAA with far less institutional support. Filing a timely NASA ASRS report remains one of the most important immediate actions a pilot can take after any suspected deviation, since it can provide limited immunity from certificate action under the FAA's Advisory Circular 00-46, provided the report is filed within ten days and the violation was not deliberate or criminal.
More broadly, this discussion reflects an enduring tension in the ATC-pilot relationship: the system depends on controllers reporting deviations to maintain safety margins and identify systemic issues, yet pilots reasonably fear that any phone call could snowball into a certificate action, insurance complications, or employment consequences. Training departments and chief pilots at airlines and larger flight departments increasingly build "what to do if you get the number" guidance into recurrent training and company policy manuals, alongside reminders about ASRS filing windows and the value of not volunteering information beyond what's requested. As ATC staffing pressures and increasingly complex airspace procedures raise the frequency of minor deviations, understanding this process—rather than reacting to it with anxiety or defensiveness—remains an essential piece of professional airmanship for every certificate holder operating in the National Airspace System.