CHI99FA047 · Piper PA-31-350
Piper PA-31-350 · Accident: in flight collision with object on approach
From Capital Region International Airport (LAN) to Oakland County International Airport (PTK)
Event
- NTSB case
- CHI99FA047
- 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
- 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
Piper PA-31-350
- Aircraft type
- Piper PA-31
- 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
- N59902
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Capital Region International Airport (LAN), Lansing, MITo Oakland County International Airport (PTK)
- 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
No findings designated as a cause are recorded in the NTSB data yet.
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The airplane collided with the tops of trees during an ILS approach near the middle marker. Witnesses heard the airplane strike the trees and a '...whop, whop, whop sound...' it made as it continued its flight. Other witnesses observed the airplane flying a curved, descending, flight path until the aircraft impacted the ground. Visibility was reported as 1/2 mile at the airport. The on-scene examination revealed no airframe or engine anomalies that would prevent flight. A section of the right propeller and other pieces of airframe were found along the approach path after initial impact with trees. The trees along the flight path were about 30 to 60 feet high. The tops of the taller trees were broken or had fresh cut marks on their limbs. The pilot's blood alcohol level was 216 (mg/dL, mg/hg).
Probable cause
the pilot's descent below the decision height for the instrument approach.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI99FA047
- Event ID
- 20001211X11519
- Case number
- CHI99FA047
- 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 1998-12-05.
- API snapshot SHA-256: 9cb92b686359760f45d24f78f9e8db11687fbabc8790721a3c70e8e8d9820868; retrieved 2026-09-20T22:18:32.186Z.