NTSB Part 830 Reporting: When a Flight School Owes the Phone Call That Cannot Wait

A 172 came back to the school late on a Saturday with the nose strut collapsed and the prop curled. The student had ballooned the flare on the third landing of a stage check, the CFI took the controls, and the touchdown was hard enough to take the firewall out of tolerance. Nobody was hurt. The CFI walked into the office and asked the chief instructor a question that should have already had a written answer: are we calling the NTSB tonight, and what does the FSDO need to know.

The two reporting obligations a school carries after an event are not the same obligation and not on the same clock. 49 CFR Part 830 is the NTSB's rule and runs on minutes. FAA notification through the local FSDO is the agency's rule and runs on its own track. A school that knows the difference, and has named the person who makes each call, has done most of the work that keeps a bad afternoon from getting worse.

What 49 CFR Part 830 Actually Covers

49 CFR Part 830 is the National Transportation Safety Board's reporting rule for civil aircraft. The rule has two verbs the operator needs to keep straight. The first is notify, which means an immediate phone call to the NTSB by the most expeditious means available. The second is report, which means a written submission, NTSB Form 6120.1, within ten days of an accident or whenever the NTSB asks for one after a serious incident.

The notify trigger fires for two distinct categories. Any aircraft accident, defined in §830.2 as an occurrence in which a person boards the aircraft with the intention of flight and during which any person suffers death or serious injury, or the aircraft receives substantial damage. And a list of named serious incidents in §830.5, regardless of whether the airplane was damaged at all.

The serious-incident list is the part flight schools tend not to know. It covers flight control system malfunction or failure, inability of any required flight crewmember to perform normal flight duties because of injury or illness, in-flight fire, aircraft collision in flight, damage to property other than the aircraft estimated above twenty-five thousand dollars, a complete loss of information from more than fifty percent of an electronic primary display, and a runway incursion that requires evasive action to prevent a collision. Several other items apply mostly to air carrier operations. The wording is specific, and the operator does not get to decide whether a borderline event counts.

Substantial Damage Is the Test Most Operators Get Wrong

The single largest source of misreported events at flight schools is the definition of substantial damage. §830.2 defines it as damage or failure which adversely affects the structural strength, performance, or flight characteristics of the aircraft, and which would normally require major repair or replacement of the affected component. The paragraph then carves out exceptions: engine failure or damage limited to an engine, bent fairings or cowling, dented skin, small punctured holes, ground damage to propeller blades, and damage to landing gear, wheels, tires, flaps, engine accessories, brakes, or wingtips.

The carve-outs are narrower than they sound. A bent firewall after a nose-gear collapse is not on the exception list. A wrinkled fuselage skin is not on the exception list. A propeller strike that bends the crankshaft is engine damage on the exception side, but the same strike that also wrinkles the firewall has crossed into substantial damage on the airframe side. A school that defaults to "the engine carve-out covers prop strikes" without inspecting the rest of the airframe is reading the rule the wrong way around.

The test the chief instructor runs on every event is whether the damage adversely affects structural strength, performance, or flight characteristics, and whether the repair will be major. If both are yes and the damage is not entirely on the exception list, the event is an accident and the NTSB phone call is owed.

The Phone Call Itself

§830.5 requires notification of the nearest NTSB office by the most expeditious means available. In practice that is the NTSB Response Operations Center, which the NTSB publishes as a single twenty-four-hour line. The required information is the aircraft type and registration, the owner and operator, the pilot in command, the date and time, the last point of departure and the point of intended landing, the aircraft's position, the persons aboard and the number injured or killed, the nature of the accident, the weather, and the extent of damage as far as it is known. The caller does not need every line filled, but the call has to be prompt enough that the agency's investigators can preserve evidence if they choose to.

The operator obligation lies on the operator. At a flight school, that is the school. The CFI on the flight, the student, and the dispatcher all have information, but the school owes the call. A written policy that names the chief instructor as the caller, with the owner as backup, removes the ten-minute hallway conversation that delays the call past the moment it is most useful.

The Ten-Day Form and the Records That Stay With the School

After an accident, §830.15 requires the operator to file NTSB Form 6120.1 within ten days. After a serious incident, the same form is filed when the NTSB requests it. The form captures the same factual scaffold as the phone call, in more detail. A school that misses the ten-day window has not met the rule.

§830.10 covers wreckage and records preservation. The operator must preserve them until the NTSB takes custody or releases them, except as needed for safety, to protect the wreckage from further damage, or to remove injured persons. That means the maintenance logbooks, the pilot logbooks, the dispatch records, the weight and balance for the flight, and the squawk record for the airframe all stay where they are. The discipline that makes aircraft squawk tracking reliable on a normal day is the discipline that produces a clean records package on an accident day.

What This Is Not

A Part 830 notification is not the same as the FAA's pilot deviation phone call and not the same as an ASRS filing. The NTSB call goes to the NTSB. The FSDO call, if the event involved a regulatory deviation, goes to the FAA. The NASA ASRS filing, if the pilot in command files one, goes to NASA and is independent of both. The insurer's claim phone call is a fourth, separate call. A school whose policy collapses these into one line ends up calling the wrong agency first or skipping one entirely.

The maintenance side has its own clock. An airplane that took substantial damage is not airworthy, and the return to service after repair is a logbook conformity question with the IA who signs it off. The dispatch system has to flag the airframe as out of service the same day, and the aircraft checkout procedure on the repaired airplane is the moment the school re-introduces it to the line.

What the Policy Should Say Before the Phone Rings

A working Part 830 policy fits on the back of the dispatch reference. It defines the trigger events that require the phone call. It names the caller and the backup. It lists the NTSB Response Operations Center number, the local FSDO number, and the insurer's claims line, in that order. It commits the school to preserving the airframe, the maintenance logs, and the pilot records until released. It states that the CFI on the flight does not move the airplane, scrub the cockpit, or write anything in the maintenance record beyond a discrepancy entry until the chief instructor and the insurer have spoken. And it ties the post-event review into the next CFI standardization meeting, where the lesson the school takes from the day becomes a change to the brief, the syllabus, or the airplane on the line.

The schools that handle the worst day well are the ones whose chief instructor already knew which call came first and who made it. The phone numbers were on the wall, the policy was on the back of the dispatch sheet, and the question the CFI asked walking off the ramp had a written answer waiting in the binder.