CHI95LA037 · Beech G35
Beech G35 · Accident: in flight collision with object on approach
From East Troy Municipal Airport (57C) to C18
Narrative check · The NTSB narrative appears to contradict this record's aircraft involved. Values are shown as recorded, not corrected; compare with the narrative.
Event
- NTSB case
- CHI95LA037
- 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
- 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
Beech G35 Possible conflict
- Aircraft type
- Beechcraft 35
- 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
- N4469D
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From East Troy Municipal Airport (57C), East Troy, WITo C18
- 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 · VFR pattern final
- 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
- 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
- Driver of vehicle › Unsafe/hazardous condition, disregarded
- Pilot in command › Visual lookout, inadequate
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
WHILE ON SHORT FINAL TO LAND, THE LEFT MAIN GEAR CONTACTED THE ROLL BAR ON A BULLDOZER WHICH WAS ON A FLAT BED TRAILER BEING PULLED BY A TRUCK. THE TRUCK HAD BEEN DRIVEN OUT OF A PARKING LOT NEXT TO THE RUNWAY AND TURNED ONTO A ROAD WHICH WAS 30 FEET FROM THE APPROACH END OF THE RUNWAY. THE PILOT STATED HE NEVER SAW THE TRUCK UNTIL AFTER HE LANDED. AFTER LANDING, THE AIRPLANE VEERED TO THE LEFT, TRAVELED OFF THE RUNWAY, AND CONTACTED A PARKED CESSNA 170 AIRPLANE. THE DRIVER OF THE TRUCK REPORTEDLY SAW THE AIRPLANE, BUT WAS NOT CONCERNED.
Probable cause
FAILURE OF THE PILOT TO SEE-AND-AVOID THE VEHICLE, AND THE VEHICLE DRIVER'S DISREGARD FOR THE NEED TO REMAIN CLEAR OF THE AIRCRAFT'S APPROACH PATH. A FACTOR RELATED TO THE ACCIDENT WAS: THE PROXIMITY OF A PARKED AIRPLANE TO THE RUNWAY.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI95LA037
- Event ID
- 20001206X02575
- Case number
- CHI95LA037
- 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: 2b4b42f61be61ea8edba879c51da68895c6a077ee1f053fa8315384f8563be60; retrieved 2026-09-21T22:26:38.284Z.