ATL83FIJ02 · Cessna 182P
Cessna 182P · Accident: in flight collision with object on approach
From 6A8 · Abingdon, VA to Mercer County Airport (BLF)
Event
- NTSB case
- ATL83FIJ02
- 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
- 0 · 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
- Instrument Meteorological Cond
Cessna 182P
- Aircraft type
- Cessna 182
- 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
- N7353S
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From 6A8 · Abingdon, VATo Mercer County Airport (BLF), Bluefield, WV
- 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 · IFR final approach
- 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
- Tree(s)
- 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 › Decision height, below
- Pilot in command › Proper glidepath, not followed
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE PLT REPORTED THAT HE BEGAN AN ILS APPROACH TO THE MERCER COUNTY ARPT. HE STATED THAT HE PLANNED TO DESCEND TO 3200 FT MSL, THEN EXECUTE A MISSED APPROACH & RETURN TO ABINGTON, VA. THE ARPT ELEVATION WAS 2857 FT MSL. HE STATED THAT HE REMEMBERED GLANCING AT THE ALTIMETER AT 3200 FT, THAT HE LOOKED FOR THE RWY ENVIRONMENT, AND THAT HE WAS PREPARING TO EXECUTE THE MISSED APPROACH, WHEN THE ACFT SUDDENLY HIT TREES & CRASHED. THE IMPACT OCCURRED APRX 1/2 MI FROM THE APPROACH END OF RWY 23. THE WEATHER WAS: 100 FT OBSCURED, VISIBILITY 1/2 MI WITH FOG, TEMP 42 DEG, WIND FROM 280 DEG AT 5 KTS. THE ILS & VORTAC FACILITIES WERE FOUND TO BE OPERATIONAL. THE ACFT NAVCOMM UNIT, GLIDE SLOPE RECEIVER & COURSE INDICATOR HEAD WERE BENCH CHECKED & FOUND TO BE WITHIN TOLERANCES. THE ALTIMETER WAS TESTED & SHOWED A CONSIDERABLE ERROR AT EACH TEST POINT; BUT WAS NOT DISASSEMBLED TO DETERMINE IF INTERIM DAMAGE HAD OCCURRED.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record ATL83FIJ02
- Event ID
- 20001214X42593
- Case number
- ATL83FIJ02
- 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: 7e89c517d5562b7e3fd07ce8601b17e75fd8b685ab7972bdc47af04ba18cc616; retrieved 2026-09-21T17:58:37.144Z.