ATL83MA084 · Beech D55
Beech D55 and McDonnell Douglas F4C · Accident: midair collision en route
Event
- NTSB case
- ATL83MA084
- Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
- Accident
- InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
- Completed
- API-reported fatalities
- 7 · all aircraft and ground
- Ground fatalities
- 0
- OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
- General aviation
- WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
- Visual Meteorological Cond
Aircraft 1 · Beech D55
- Aircraft type
- Beechcraft 55
- Category
- Airplane
- RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
- N7142N
- Operator
- Henry H. Tiffany · private individual
- Onboard fatalities
- Unknown
- Route
- From Nassau, BAHAMASTo Norfolk International Airport (ORF), Norfolk, VA
- Aircraft age
- Not recorded
- Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
- Part 91: General Aviation
- Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
- En route · cruise
- First occurrenceThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
- Midair collision
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Destroyed
Aircraft 2 · McDonnell Douglas F4C
- Aircraft type
- McDonnell Douglas F4
- Category
- Airplane
- RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
- AFNG
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Seymour Johnson Air Force Base (KGSB), Goldsboro, NCTo not recorded
- Aircraft age
- Not recorded
- Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
- Armed Forces
- Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
- Maneuvering
- First occurrenceThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
- Midair collision
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Substantial
Cause areas
No findings designated as a cause are recorded in the NTSB data yet.
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE TWO ACFT COLLIDED AT ABOUT 9,500 FT MSL 30 MI SOUTH OF CHERRY POINT. AFTER DEPARTING NASSAU, THE PLT OF THE BE-D55 NEVER ACTIVATED HIS FLT PLAN. AN ADIZ PENETRATION TIME WAS THEREFORE NEVER ESTABLISHED. WHEN THE UNIDENTIFIED ACFT ENTERED WARNING AREA W-122, THE USAF CONTACTED FAA ATC FOR IDENTIFICATION INFO. SINCE FAA WAS NOT CONTROLLING ANY TRAFFIC IN THAT AREA AN INTERCEPT ORDER WAS ISSUED. AT 1637 FAA GOT A POSITION REPORT FROM THE BE-D55 & RELAYED IT TO MILITARY CONTROL. HOWEVER, THE TWO FIGHTER ACFT CONTINUED TO CLOSE IN ON THE TARGET FOR RADAR CONTACT. THE LEAD ACFT WAS TO CLOSE ABOUT 1,000 FT BELOW THE TARGET AT A PREPLANNED CLOSURE RATE OF 50 KTS (ACTUAL RATE WAS 127 KTS). SECONDS BEFORE THE COLLISION, THE BE-D55 TURNED LEFT AS REQUESTED BY FAA ATC THUS TURNING IT INTO THE PATH OF THE OVERTAKING INTERCEPTOR WHICH ALSO HAD TURNED LEFT TO BREAK OFF THE INTERCEPT. THE SAFETY BOARD DID NOT DETERMINE THE PROBABLE CAUSE OF THIS ACCIDENT, BUT OFFERED STATEMENTS OF CAUSE.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record ATL83MA084
- Event ID
- 20001214X41935
- Case number
- ATL83MA084
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
Source notes (4)
- Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
- Filled from the NTSB case API where the bulk record had no value: investigation status. Values present in the bulk record are kept.
- The date is the local date, which is the same as the UTC date the NTSB stores.
- API snapshot SHA-256: 944c5794cf09c2858324d1f230d1f796d4f684caa0876f73cfc7c6a3d300cedf; retrieved 2026-09-21T07:16:57.775Z.