CHI93LA337 · Piper AEROSTAR 601P AEROSTAR 6
Piper AEROSTAR 601P AEROSTAR 6 · Accident: overrun during landing
From Aurora Municipal Airport (ARR) to Welke Airport (6Y8)
Event
- NTSB case
- CHI93LA337
- 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
Piper AEROSTAR 601P AEROSTAR 6
- Aircraft type
- Piper AEROSTAR 601
- 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
- N479CB
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Aurora Municipal Airport (ARR), Aurora, ILTo Welke Airport (6Y8)
- 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
- Overrun
- 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
- Pilot in command › Planning/decision, improper
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
DURING A LANDING, THE AIRPLANE OVERRAN THE RUNWAY & STOPPED ABOUT 125 FEET BEYOND THE DEPARTURE END WITH A COLLAPSED NOSE GEAR. THE PILOT INDICATED HE THOUGHT THE WIND WAS FROM ABOUT 180 DEGREES AT 10 GUSTING 15 KNOTS. ABOUT 32 MILES EAST-SOUTHEAST AT PELLSTON, MI, THE WIND WAS FROM 250 DEGREES AT 20 KNOTS. THE AIRPLANE LANDED ON RUNWAY 9, WHICH WAS 2682 FEET LONG; IT HAD AN EFFECTIVE LANDING LENGTH OF 2157 FEET DUE TO A 525 FOOT DISPLACED THRESHOLD, WHICH IN TURN WAS DUE TO TREES. THE AEROSTAR 601 OWNERS MANUAL SHOWED A REQUIRED LANDING DISTANCE OF 2180 FEET (FOR 5000 LBS GROSS WEIGHT, ZERO WIND, 45 DEGREES FLAPS, SEA LEVEL & A 3 DEGREE APPROACH ANGLE). THE PILOT STATED THAT AN AIRPORT GUIDE (THAT HE USED FOR PLANNING PURPOSES) LISTED THE RUNWAY AS 2650 FEET, AND WHEN HE TALKED WITH THE OPERATORS OF THE AIRPORT, THEY TOLD HIM THE RUNWAY WAS 3500 FEET LONG. A POST-ACCIDENT INSPECTION FAILED TO REVEAL ANY MECHANICAL PROBLEM WITH THE BRAKE SYSTEM.
Probable cause
IMPROPER PLANNING/DECISION BY THE PILOT. FACTORS RELATED TO THE ACCIDENT WERE: THE UNFAVORABLE WIND, AND HIGH OBSTRUCTIONS NEAR THE END OF THE RUNWAY.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI93LA337
- Event ID
- 20001211X13117
- Case number
- CHI93LA337
- 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: f173b37c163bd7e292722ab351bd8bb4da25b6ce14bd2a00c4178a8c9f2cc6cc; retrieved 2026-09-23T01:42:38.616Z.