CEN25LA370 · Boeing E75
Boeing E75 · Accident: collision with terrain/object (non-CFIT) on approach
From Gardner Municipal Airport (K34) to an unrecorded destination
Event
- NTSB case
- CEN25LA370
- 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
- Event fatalities
- Unknown
- 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
Boeing E75
- Aircraft type
- Boeing E75
- 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
- N75675
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Gardner Municipal Airport (K34), Gardner, KSTo not recorded
- Aircraft age
- About 82 years (built 1943)
- 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
- 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
- Aircraft › Aircraft oper/perf/capability
- Environmental issues › Physical environment
- 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
The pilot was in the traffic pattern for the private airport and planning to land in the grass next to the paved runway. As the pilot made a turn to final approach, he heard another airplane report being “short final” for the same runway. The pilot and passenger attempted to make visual contact with the other airplane. Unable to make visual contact with the other airplane, the pilot elected to quickly land his airplane. The pilot conducted a forward slip during his descent, and the airplane’s main landing gear impacted an automobile that was being driven on the adjacent roadway near the approach end of the runway. The airplane landed hard in the grass and came to rest inverted resulting in substantial damage to the vertical stabilizer, rudder, upper right and left wings, and both wing struts. The pilot reported no preimpact mechanical malfunctions or failures with the airplane that would have precluded normal operation. The displaced threshold for the landing runway was located about 242 ft from the approach end of the runway. The roadway that crossed the extended runway centerline was located about 36 ft from the approach end of the runway pavement, about 278 ft from the displaced threshold. The (Obstacle) Departure Procedures for the airport list vehicles on road beginning 20 ft from the runway and left and right of centerline. According to the pilot, after the accident it was reported that the other airplane was about 5 miles from the airport when that pilot radioed he was on “short final” for the runway. The Aeronautical Information Manual states that inbound pilots should self-announce on UNICOM when they are 10 miles out, entering downwind, base, final, and when leaving the runway.
Probable cause
The pilot's failure to maintain clearance from a moving vehicle during an evasive maneuver from a perceived conflict with another airplane. Contributing to the accident was the pilot of the other airplane’s non-standard phraseology and inaccurate position report.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN25LA370
- Event ID
- 20250908200958
- Case number
- CEN25LA370
- 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, cause areas. 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: 40c944d5b4f40d1e2ee650d31cefefe8c44ccaa990b37f763c07b5d49df33529; retrieved 2026-09-16T20:18:49.053Z.