ERA14CA366 · Cessna 150M
Bux Aviation Cessna 150M · Accident: controlled flight into terrain/object (CFIT) on approach
From Match Mate Airport (NK74) to D93 · Waterloo, NY
Event
- NTSB case
- ERA14CA366
- 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
- 0 · 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
- Visual Meteorological Cond
Cessna 150M
- Aircraft type
- Cessna 150
- 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
- N66358
- Operator
- Bux Aviation
- Onboard fatalities
- Unknown
- Route
- From Match Mate Airport (NK74), Aurora, NYTo D93 · Waterloo, NY
- Aircraft age
- About 40 years (built 1974)
- 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 pattern final
- 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
- Controlled flight into terrain/object (CFIT)
- 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
- Wire
- 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
- Aircraft › Aircraft oper/perf/capability
- Personnel issues › Action/decision
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
Prior to departing on the flight, the pilot referenced the Airport/Facility Directory and noted that one of the runways at the destination airport had a displaced threshold. He subsequently departed, and entered the traffic pattern to land on the 2,275-foot turf runway 28, approaching the end with the displaced threshold. The pilot became concerned with the runway's relatively short length, and on final approach, increased the airplane's descent angle in order to use as much of the runway as possible. While on short final approach, the pilot suddenly observed marked power lines that ran perpendicular to the runway, across the threshold, and immediately thereafter one of the main landing gear wheels struck the wire. The airplane then yawed to the left and pitched nose-down. The pilot attempted to correct the upset, but the airplane subsequently struck the ground, resulting in substantial damage to the airframe. The power lines were depicted in airport information.
Probable cause
The pilot's failure to maintain adequate clearance from obstructions while on approach to the runway.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA14CA366
- Event ID
- 20140729X61607
- Case number
- ERA14CA366
- 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, coordinates. 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: a202c1a22792e3f1551a8087e926f860e038e9cb6a4737845c3cca4c1b51104f; retrieved 2026-09-16T01:01:34.396Z.