A flight instructor and student pilot conducting practice instrument approaches into a Class D airport committed an airspace incursion by entering the delta without establishing two-way radio communication with the tower — a direct violation of 14 CFR 91.129. The sequence unfolded when approach control cleared the crew for the approach and instructed them to contact tower, but task saturation on the part of both occupants resulted in the frequency change being missed entirely. The crew did not contact tower until they were already inside the Class D on a two-mile final. Although the tower cleared them to land and no pilot deviation (PD) was issued, the regulatory violation had already occurred the moment the aircraft crossed the Class D boundary without having established contact. The absence of a PD notification does not extinguish the violation; it merely indicates the controller either did not notice, chose not to file, or the situation resolved without operational conflict.
Filing a NASA Aviation Safety Reporting System (ASRS) report is strongly advisable in this situation, and the answer to the question posed is an unambiguous yes. The ASRS program, administered by NASA under an agreement with the FAA, provides a conditional shield against certificate action for inadvertent violations that are reported voluntarily and in good faith. To qualify for that immunity, the violation must not have been deliberate, the pilot must not have committed a similar violation within the preceding five years for which a certificate action was taken, and — critically — the report must be submitted within 10 days of the incident. Both the instructor and the student should file separate reports, as both were pilots in command for their respective regulatory purposes and both bear responsibility for the breakdown. The 10-day window is not soft; missing it forfeits the protection entirely.
Task saturation in a dual-pilot training environment carries a specific and frequently underestimated risk profile. When an instructor shifts cognitive resources toward managing a struggling student, the instructor's own scan and checklist discipline can degrade — exactly the scenario described here. This is sometimes called the "instructor trap," where the teaching role inadvertently suppresses the safety-pilot role. A sterile cockpit concept, even in a training context, demands that critical communications never be subordinated to instructional dialogue. The frequency change to tower after an approach clearance is a high-priority, time-sensitive action, and its omission in this case illustrates how easily automation complacency and divided attention can produce regulatory exposure even when the flight outcome is benign.
Viewed against the broader landscape of airspace incursion trends, Class D incidents of this type are among the most common and the most preventable. The FAA's Runway Safety and Airspace Program data consistently identifies communication failures — missed frequency changes, incorrect frequencies, and delayed contact — as a leading causal factor in Class D incursions. The FAA has also increased scrutiny of flight training operations in recent years, particularly where CFIs are involved in deviation chains, given the certification implications and the downstream safety modeling that instructors represent. Filing the ASRS report serves not only the individual pilots' legal interests but also contributes anonymized data to the safety ecosystem that helps identify systemic patterns. The ASRS database has directly informed regulatory and procedural changes in U.S. airspace management, making voluntary reporting an active contribution to systemic safety rather than merely a self-protective act.