CHI98FA288 · Hispano Aviacion A10B-37
Hispano Aviacion A10B-37 · Accident: in flight collision with object on approach
From Purdue University Airport (LAF) to Wittman Regional Airport (OSH)
Event
- NTSB case
- CHI98FA288
- 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
- Visual Meteorological Cond
Hispano Aviacion A10B-37
- Aircraft type
- Hispano Aviacion A10
- 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
- N2741P
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Purdue University Airport (LAF), Lafayette, INTo Wittman Regional Airport (OSH)
- 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
- 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); Utility pole
- 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
- Object › Tree(s)
- Pilot in command › Altitude, inadequate
- Reason for occurrence undetermined
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
A witness, who was flying in the traffic pattern, observed the jet cross the shoreline heading westbound at around 50 to 75 feet above the ground. The airplane then made an abrupt turn from west to north. The witness saw the jet descend into the trees and then he saw a fireball. Witnesses on the ground observed the airplane make a hard descending right turn, strike a power pole, and then impact the ground The pilot said that on the approach, the airplane 'developed a high sink rate of descent.' He felt that he did not get the throttles up fast enough to arrest the descent and that the right engine suffered a compressor stall. Examination of the left engine revealed foreign object damage while there was no foreign object damage to the right engine.
Probable cause
the pilot's failure to maintain adequate altitude which resulted in in-flight collision with trees and subsequent compressor stall for undetermined reasons.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI98FA288
- Event ID
- 20001211X10780
- Case number
- CHI98FA288
- 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: ecd010090ba4172a6eae7b4b3c430b2802f0e3f411da0ebf9a687a65f5031a18; retrieved 2026-09-20T22:28:52.001Z.