ATL83FIJ01 · Piper PA-28-161
Sunrise Aviation Enterprises Piper PA-28-161 · Accident: in flight collision with object during landing
From Batavia, OH to TAPLIN, WV
Event
- NTSB case
- ATL83FIJ01
- 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
- 2 · 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
Piper PA-28-161
- Aircraft type
- Piper PA-28
- 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
- N8249K
- Operator
- Sunrise Aviation Enterprises
- Onboard fatalities
- Unknown
- Route
- From Batavia, OHTo TAPLIN, 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
- Landing
- 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
- Substantial
Cause areas
- Pilot in command › Airspeed, misjudged
- Pilot in command › Distance, misjudged
- Pilot in command › Go-around, delayed
Approximate · Estimated position: the centre of Man, WV, the place the record names. Not the accident site.
NTSB narrative
A WITNESS REPORTED THAT THE PILOT LANDED ABOUT 2100 FT DOWN THE 2750 FT, TURF RUNWAY, ROLLED SEVERAL HUNDRED FEET, THEN ATTEMPTED TO GO AROUND. WHEN THE AIRCRAFT WAS ABOUT 4 OR 5 FT IN THE AIR, IT HIT SOME TREES WHILE HEADING INTO A RIVER BASIN NEAR THE END OF THE RUNWAY. THE LEFT WING HIT A SUSPENSION FOOT BRIDGE AS THE PLANE CROSSED UNDER THE BRIDGE. THE AIRCRAFT THEN CRASHED INTO THE RIVER BANK. AN EXAMINATION OF THE ENGINE WAS MADE, BUT NO PREIMPACT MALFUNCTION WAS FOUND. A WITNESS REPORTED THAT THE WIND FAVORED RUNWAY 32. ANOTHER WITNESS WAS IN AN AIRCRAFT GETTING READY TO DEPART ON RUNWAY 32 WHEN THE ACCIDENT OCCURRED.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record ATL83FIJ01
- Event ID
- 20020917X04319
- Case number
- ATL83FIJ01
- 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: 50e442ed61dc149720346f36032cea623cc5ca85ca9019a555f9e107e75e9ea2; retrieved 2026-09-21T07:28:41.745Z.