Overall Trends
Total, fatal, and serious accidents in the selected range.
Search investigations, review source evidence, monitor watched reports, and trace long-term patterns from one calm, data-first workspace.
Fast key and full-text search with live filters, watches, and precise metadata.
Use quotes for exact phrase matches (for example "fuel selector valve").
Track fatal and non-fatal accident patterns across Part 91, Part 135, and Part 121 operations.
Major cases, deep-report coverage, and investigation media across decades of NTSB history.
Move quickly by aircraft, airport, operator, and time with indexes built for research, not wandering.
NTSB Reports is an independent research and search tool for public aviation accident and incident records. It brings NTSB aviation reports, structured fields, docket files, extracted figures, photos, videos, and update history into one searchable interface.
The goal is practical safety education: make it faster to find relevant investigations, compare similar events, review factual records, and understand the evidence behind probable-cause and preliminary reports.
The investigative work and source records belong to the National Transportation Safety Board and the published investigation record. This site is not affiliated with or endorsed by the NTSB.
Marietta, GA
Eastern Airlines Flight 92, a Boeing 727, N8840E, and an Air Force KC-135, Reg #60-0330, call sign FOWL 24, were involved in a near collision while both aircraft were maintaining FL350. The captain of Flight 92 reported that during the occurrence, the KC-135 passed directly in front of his aircraft at a distance of about 1/4 mile, crossing from right to left. Also, he reported that there was insufficient time for him to avoid wake turbulence from the KC-135. The KC-135 flight crew were unaware of the occurrence until after they had completed their training flight. An investigation revealed that the incident occurred after Jacksonville Center had instructed the KC-135 crew to contact Atlanta Center during a hand-off. The KC-135 copilot thought he had complied, but no calls were recorded until after the incident. The Atlanta controller was not aware of the KC-135 in his assigned airspace until after the captain of Flight 92 reported the near collision. The investigation revealed that radar data on the KC-135 was available and displayed on the controller's scope.
EASTERN AIRLINES FLT 92, A BOEING 727, N8840E, AND AN AIR FORCE KC-135, REG #60-0330, CALL SIGN FOWL 24, WERE INVOLVED IN A NEAR COLLISION WHILE BOTH ACFT WERE MAINTAINING FL350. THE CAPTAIN OF FLT 92 REPORTED THAT DURING THE OCCURRENCE, THE KC-135 PASSED DIRECTLY IN FRONT OF HIS ACFT AT A DISTANCE OF ABOUT 1/4 MI, CROSSING FROM RIGHT TO LEFT. ALSO, HE REPORTED THAT THERE WAS INSUFFICIENT TIME FOR HIM TO AVOID WAKE TURBULENCE FROM THE KC-135. THE KC-135 FLT CREW WERE UNAWARE OF THE OCCURRENCE UNTIL AFTER THEY HAD COMPLETED THEIR TRAINING FLT. AN INVESTIGATION REVEALED THAT THE INCIDENT OCCURRED AFTER JACKSONVILLE CENTER HAD INSTRUCTED THE KC-135 CREW TO CONTACT ATLANTA CENTER DURING A HAND-OFF. THE KC-135 COPLT THOUGHT HE HAD COMPLIED, BUT NO CALLS WERE RECORDED UNTIL AFTER THE INCIDENT. THE ATLANTA CONTROLLER WAS NOT AWARE OF THE KC-135 IN HIS ASSIGNED AIRSPACE UNTIL AFTER THE CAPTAIN OF FLT 92 REPORTED THE NEAR COLLISION. THE INVESTIGATION REVEALED THAT RADAR DATA ON THE KC-135 WAS AVAILABLE & DISPLAYED ON THE CONTROLLER'S SCOPE.