IAD03FA001 · Piper Aerostar 602P
Piper Aerostar 602P · Accident: in flight collision with terrain/water on approach
From Evansville Regional Airport (EVV) to Bradford Regional Airport (BFD)
Event
- NTSB case
- IAD03FA001
- 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 Aerostar 602P
- Aircraft type
- Piper AEROSTAR 602
- 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
- N700DJ
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Evansville Regional Airport (EVV), Evansville, INTo Bradford Regional Airport (BFD), Bradford, 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 · IFR initial 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 terrain/water
- 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 › IFR procedure, not followed
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The pilot attempted an ILS approach during night, instrument meteorological conditions. The inbound course was 322 degrees magnetic, and the glideslope outer marker crossing altitude was 3,333 feet msl. The decision altitude was 2,370 feet msl and the airport elevation was 2,143 feet msl. A wreckage path, about 370 feet in length, along a track 320 degrees magnetic, commenced with a tree strike about 300 feet southeast of the outer marker, at an elevation of about 2,200 feet msl. Examination of the airplane revealed no mechanical anomalies.
Probable cause
The pilot's failure to follow the published instrument approach procedure, which resulted in an early descent into trees and terrain. A factor was the night, instrument meteorological conditions.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record IAD03FA001
- Event ID
- 20021018X05332
- Case number
- IAD03FA001
- 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, coordinates. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2002-10-04.
- API snapshot SHA-256: 51d0b602e3e5d3c60c2e1831f10bcaf272da9e0aec56b75ebe3ecf639fa203c5; retrieved 2026-09-20T19:44:37.960Z.