ERA09LA124 · Piper PA-28-160
Piper PA-28-160 · Accident: collision with terrain/object (non-CFIT) on approach
From Indiana County–Jimmy Stewart Airport (IDI) to Indiana County–Jimmy Stewart Airport (IDI)
Event
- NTSB case
- ERA09LA124
- 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
- 1 · all aircraft and ground
- Ground fatalities
- Unknown
- 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
Piper PA-28-160
- 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
- N5212W
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Indiana County–Jimmy Stewart Airport (IDI), Indiana, PATo Indiana County–Jimmy Stewart Airport (IDI), Indiana, PA
- 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
- Defining eventThe 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
- Collision with terrain/object (non-CFIT)
- 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
- Personnel issues › Action/decision
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot and two passengers took off with the intent to fly around the traffic pattern. The automated weather reporting system for the field reported steadily deteriorating conditions from earlier in the day and up to the time of departure, with instrument meteorological conditions prevailing throughout the flight. The pilot was not instrument rated and the airplane was not equipped for instrument flight. The flight continued after twilight into full darkness. The pilot stated that he encountered fog that obscured his view of the runway. After five unsuccessful approaches, the pilot stated that he could see the lights on runway 28, which was mostly behind the airplane. The pilot elected to make one more go around and attempt to land on the runway; the airplane impacted trees 1,200 feet northwest of the runway. The airplane came to rest inverted. The pilot stated that he had no intentions of flying that day due to the weather. He said that he was only to going to refuel the airplane, but one of the passengers convinced him to take the airplane once in the pattern.
Probable cause
The pilot's decision to attempt VFR flight in IMC conditions, resulting in a collision with trees during a go-around.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA09LA124
- Event ID
- 20090105X05515
- Case number
- ERA09LA124
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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: 6f650f3ee1017bcd4839fd65db1a43c8b8ca8336cc71ace44212e73473ad1be6; retrieved 2026-09-13T19:54:11.368Z.