CHI83FA381 · Beech G18S
Beech G18S · Accident: in flight collision with object during initial climb
From an unrecorded airport to Kenosha Regional Airport (ENW)
Event
- NTSB case
- CHI83FA381
- 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
- 2 · 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
- Charter & commuter
- 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 G18S
- Aircraft type
- Beechcraft 18
- 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
- N400NA
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From not recordedTo Kenosha Regional Airport (ENW), Kenosha, WI
- 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 135: Air Taxi & Commuter
- 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
- Initial climb
- 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
- Reason for occurrence undetermined
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE ACFT COLLIDED WITH A UTILITY POLE AND A LARGE TREE DURING A FORCED LANDING AFTER A POWER LOSS ON TAKEOFF. WITNESSES HEARD THE ACFT BACKFIRING AND THE GROUND RUN WAS EXCESSIVELY LONG. IMMEDIATELY AFTER TAKEOFF THE ACFT WENT THROUGH THE TOPS OF PINE TREES. THE BACKFIRING AND SMOKE STOPPED AFTER THE COLLISION WITH THE PINE TREES AND THE ACFT STARTED A DESCENT TOWARD A STREET. IT MANEUVERED AS IF TO AVOID A COLLISION WITH CARS. AFTER THE ACCIDENT THE SPARK PLUGS FROM THE RIGHT ENGINE WERE TESTED AND ALL BUT #5 FRONT PLUG WOULD NOT SPARK. HOWEVER DURING A SUBSEQUENT TEST THE SPARK PLUGSPLUGS, WITH THE EXCEPTION OF #5, DID TEST PROPERLY. A COMPLETE ENGINE TEARDOWN DID NOT REVEAL EVIDENCE OF MECHANICAL FAILURE OR PRE-IMPACT ENGINE DISCREPANCY.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record CHI83FA381
- Event ID
- 20001214X44039
- Case number
- CHI83FA381
- 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: 5affecf209358dcdfbd1eb8c4d1dd050492cc17b85783b9ecacba401bdb9ecf0; retrieved 2026-09-18T14:30:19.417Z.