CHI85FA138 · Beech 58
Rynes Aviation Beech 58 · Accident: propeller blast or jet exhaust/suction while taxiing
From Detroit Metropolitan Wayne County Airport (DTW) to Chicago O'Hare International Airport (ORD)
Event
- NTSB case
- CHI85FA138
- 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 58
- Aircraft type
- Beechcraft 58
- 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
- N1889L
- Operator
- Rynes Aviation
- Onboard fatalities
- Unknown
- Route
- From Detroit Metropolitan Wayne County Airport (DTW), Detroit, MITo Chicago O'Hare International Airport (ORD)
- 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
- Taxi · from runway
- 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
- Propeller blast or jet exhaust/suction
- 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
- Atc personnel(lcl/gnd/clnc) › Control tower service, inadequate
- Atc personnel(lcl/gnd/clnc) › Instructions, written/verbal, improper
Approximate · Estimated position: the centre of Chicago, IL, the place the record names. Not the accident site.
NTSB narrative
THE BEECH 58 PLT WAS RETURNING AT NGT WHEN TRAFFIC WAS VERY LIGHT. AFTER LNDG, THE ACFT WAS RETAINED ON LOCAL CONTROL (LC) FREQ FOR THE PLT'S CONVENIENCE. THE PLT REQUESTED CLNC TO THE TWA HANGAR & WAS CLEARED ON THE MOST EXPEDITIOUS ROUTE. THIS ROUTE WENT NEXT TO THE RWY 9L PAD, WHERE A BOEING 747 MAINT CREW WERE RUNNING UP/TRIMMING ENGS. THE BEECH WAS BLOWN OVR AS IT PASSED BEHIND THE BOEING. DURING THE OCCURRENCE, THE TOP OF THE BEECH WAS CRUSHED INWARD, FATALLY INJURING THE PLT. TOWER LETTER OF OPNS PROHIBITED THE USE OF TAXIWAY NEXT TO THE RWY 9L PAD, WHEN IT WAS BEING USED FOR RUN-UPS. THE BEECH PLT WAS NOT CAUTIONED ABOUT PSBL WAKE TURBC & THE BOEING CREW WERE NOT ADVISED OF THE BEECH'S PSN. FOR REASONS OF NOISE ABATEMENT, THE NGT-TIME RUN-UP OF THE BOEING 747 SHOULD HAVE BEEN CONDUCTED ON A HDG OF EAST OR NORTHWEST, BUT THE 747 WAS ON A HDG OF SOUTHWEST, ANGLED INTO THE WIND. NONE OF THE FOUR TOWER CONTROLLERS DETECTED OR ATTEMPTED CORRECTING ITS ORIENTATION.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record CHI85FA138
- Event ID
- 20001214X35859
- Case number
- CHI85FA138
- 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: 2752748d6c8a5aaa0d5d54eb4f9a00b9dcf32d7953be960ba315498f86c7b44b; retrieved 2026-09-21T05:06:50.608Z.