CHI93FA180 · Beech C-18S
Beech C-18S · Accident: nose over during landing
From Al's Due North Airport (MY90) to Al's Due North Airport (MY90)
Event
- NTSB case
- CHI93FA180
- 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
Beech C-18S
- Aircraft type
- Beechcraft C-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
- N67E
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Al's Due North Airport (MY90)To Al's Due North Airport (MY90)
- 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
- Landing · landing roll
- 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
- Nose over
- 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
- Pilot in command › Brakes(normal), excessive
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE FLIGHT ORIGINATED AT 1235. THE PILOT PERFORMED TWO FLY-BY PASSES FOR THE DEDICATION OF A NEARBY MALL. THE PILOT RADIOED FOR CLEARANCE TO LAND AT THE PRIVATE AIRPORT WHICH HE OWNED. HE WAS GIVEN CLEARANCE TO LAND AND TOLD THE WIND WAS FROM THE SOUTH AT 20 KTS. THE PILOT LANDED ON RUNWAY 09. DURING LANDING ROLL, THE AIRPLANE WAS SEEN TO NOSE OVER. THE COCKPIT, CABIN, AND LEFT WING OF THE AIRPLANE WERE CONSUMED BY FIRE. THE PASSENGER ESCAPED THROUGH THE OVER-WING EMERGENCY EXIT ON THE RIGHT SIDE OF THE CABIN. HE STATED THE PILOT WAS LYING NEAR THE REAR DOOR AND WOULD NOT RESPOND TO STIMULUS. THE INVESTIGATION REVEALED TWO SKID MARKS IN THE GRASS WHICH TERMINATED AT THE AIRPLANE WRECKAGE. THE MARK MADE BY THE RIGHT MAIN LANDING GEAR WAS 750 FEET LONG. THE SKID MARK MADE BY THE LEFT MAIN LANDING GEAR WAS 560 FEET LONG.
Probable cause
excessive use of brakes by the pilot-in-command.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI93FA180
- Event ID
- 20001211X12341
- Case number
- CHI93FA180
- 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: 6c863b7f7265b6ec3574cc2d70a4b263c1bb82dbe407f39be60d4d78463150fb; retrieved 2026-09-21T00:33:06.573Z.