ATL83FA163 · Beech V35B
Beech V35B · Accident: in flight collision with object on approach
From Norfolk International Airport (ORF) to an unrecorded destination
Event
- NTSB case
- ATL83FA163
- 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
- 4 · 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
Beech V35B
- Aircraft type
- Beechcraft 35
- 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
- N9394Q
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Norfolk International Airport (ORF), Norfolk, VATo 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
- 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
- Approach · VFR go-around
- 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
- In flight collision with object
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Wire, transmission
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Destroyed
Cause areas
- Pilot in command › In-flight planning/decision, improper
- Pilot in command › Judgment, poor
- Pilot in command › Proper climb rate, not maintained
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE DESTINATION ARPT WAS UNLIGHTED & WAS CLOSED FROM 30 MIN AFTER SUNSET UNTIL 30 MIN BEFORE SUNRISE. PRIOR TO THE FLT, THE PLT MADE ARRANGEMENTS FOR SOMEONE TO TAKE HIS CAR TO THE DESTINATION ARPT & PARK IT WITH THE HEADLIGHTS TURNED ON AT THE APCH END OF RWY 06. THE ACFT ARRIVED AFTER DARK. THE PERSON THAT BROUGHT THE CAR TO THE ARPT, REPORTED THAT THE PLT MADE SEVERAL LOW APCHS TO RWY 06. EACH TIME, THE PLT EXECUTED A GO-AROUND. THE WITNESS NOTED THAT THE SOUTHWEST WIND WAS "ROCKING THE PLANE AROUND QUITE A BIT," THAT THE ACFT WAS NOT LINED UP VERY WELL, & THAT THE THERE WAS A STRONG X-WIND COMPONENT FROM THE QUARTERING TAIL WIND. AFTER ABOUT THE 7TH APPROACH, THE ACFT DRIFTED RIGHT OF THE RWY & LOST ALTITUDE DURING THE GO-AROUND; THEN HIT A POWER LINE, CRASHED & BURNED.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record ATL83FA163
- Event ID
- 20001214X42589
- Case number
- ATL83FA163
- 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: local date, investigation status. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 1983-04-16.
- API snapshot SHA-256: 17b6e3ff94dbfbde5b5766ae77897586918004917be9ecbb31cd26be01272cd7; retrieved 2026-09-21T06:54:27.074Z.