FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

MKC89LA200 · Hughes 269C

28 Sept 1989 · Bloomington, MN, United States

J.R. Copter Hughes 269C · Accident: total loss of engine power (mechanical failure) en route

From Saint Paul Downtown Holman Field (STP) to Saint Paul Downtown Holman Field (STP)

Report a problem

Event

NTSB case
MKC89LA200
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

Hughes 269C

Aircraft type
Hughes 269
Category
Helicopter
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
N95KS
Operator
J.R. Copter
Onboard fatalities
Unknown
Route
From Saint Paul Downtown Holman Field (STP), ST PAUL, MNTo Saint Paul Downtown Holman Field (STP)
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
En route · cruise
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
Total loss of engine power (mechanical failure)
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

  • Engine assembly, crankshaft › Failure, total

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

THE HELICOPTER WAS BEING FLOWN ON AN EARLY MORNING, RUSH HOUR, TRAFFIC WATCH. THE PLT RPRTD THE HELICOPTER WAS AT ABOUT 500 FT AGL & 20 KTS WHEN THE ENG FAILED. HE BEGAN AN AUTOROTATION TO A PARKING LOT. JUST BEFORE LANDING, HE SAW THE LIGHTS OF A CAR AS IT ENTERED INTO THE PARKING LOT. WITH PARKED CARS ELSEWHERE IN THE PARKING LOT, HE ELECTED TO SHORTEN HIS APCH PATH TO LAND IN ANOTHER AREA. AFTER SLOWING THE HELICOPTER TO LAND AT THE ALTERNATE LOCATION, THERE WAS INSUFFICIENT INERTIA LEFT IN THE ROTOR BLADES TO CUSHION THE LANDING. THE HELICOPTER TOUCHED DOWN HARD, DAMAGING THE UNDERCARRIAGE. AN EXAM OF THE ENG REVEALED THE CRANKSHAFT HAD FAILED BETWEEN THE #2 & #3 CHEEKS. THE ENG HAD A TOTAL OPERATIONAL TIME OF 2373 HRS & HAD 998 HRS OF OPERATION SINCE THE LAST OVERHAUL.

Probable cause

FAILURE OF THE ENGINE CRANKSHAFT. THE LIGHT CONDITIONS AT DAWN AND THE VEHICLES WERE CONSIDERED TO BE CONTRIBUTING FACTORS.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record MKC89LA200
Event ID
20001213X29466
Case number
MKC89LA200
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: 298f4ebc4443f25da6524487d27fc3b14f1ed298dc8d63d7947a62b9eb4cf3bc; retrieved 2026-09-23T07:07:39.015Z.