FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CHI93GA046 · Schweizer 269C

1 Dec 1992 · Kansas City, MO, United States

Board of Police Commissioners Schweizer 269C · Accident: airframe, component or system failure en route

From an unrecorded airport to Police Department Helicopter Maint Facility Heliport (3MO1)

Report a problem

Narrative check · The NTSB narrative appears to contradict this record's operation. Values are shown as recorded, not corrected; compare with the narrative.

Event

NTSB case
CHI93GA046
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
General aviation Possible conflict
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

Schweizer 269C

Aircraft type
Schweizer 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
N640KC
Onboard fatalities
Unknown
Route
From not recordedTo Police Department Helicopter Maint Facility Heliport (3MO1)
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
Airframe, component or system failure
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 › Distance, misjudged

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

NTSB narrative

WHILE ON A ROUTINE NIGHT PATROL THE POLICE HELICOPTER EXPERIENCED THE LOSS OF THE LARGE CLEVIS PIN IN THE CLUTCH CONTROL SPRING ASSEMBLY. THE LOSS OF THE SPRING ASSEMBLY DISCONNECTED THE POWERPLANT FROM THE ROTOR SYSTEM. THE PILOT INITIATED AN AUTOROTATION. THE TERRAIN UNDERLYING THE LANDING ATTEMPT WAS A RAVINE WITH HIGH TREES. THE PILOT WAS NOT ABLE TO JUDGE THE DISTANCE BETWEEN THE HELICOPTER AND THE GROUND TO SUCCESSFULLY EFFECT AN AUTOROTATIONAL LANDING.

Probable cause

THE PILOT-IN-COMMAND'S MISJUDGING THE DISTANCE DURING THE AUTOROTATION.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CHI93GA046
Event ID
20001211X16133
Case number
CHI93GA046
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: local date, investigation status. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 1992-12-02.
  • API snapshot SHA-256: 4f966054a3837b5c99029480ba8d86c87e3dd1337a90a323e752623b7e7f9a18; retrieved 2026-09-21T00:47:09.625Z.