CHI93LA159 · Schweizer 269C
University of North Dakota Schweizer 269C · Accident: loss of control on ground/water during landing
Narrative check · The NTSB narrative appears to contradict this record's damage. Values are shown as recorded, not corrected; compare with the narrative.
Event
- NTSB case
- CHI93LA159
- 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
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
- N7504D
- Operator
- University of North Dakota
- Onboard fatalities
- Unknown
- Route
- From not recordedTo not recorded
- 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 · flare/touchdown
- 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
- Loss of control on ground/water
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Substantial Possible conflict
Cause areas
- Pilot in command › Collective, not used
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE PILOT WAS PRACTICING LANDINGS WHEN THE ACCIDENT OCCURRED. THE PILOT STATED HE LOWERED THE COLLECTIVE AND CENTERED THE CYCLIC IN ORDER TO STOP A GROUND RUN DURING THE LANDING. THE HELICOPTER BEGAN TO VIBRATE AND THE PILOT BROUGHT THE CYCLIC BACK TO CENTER, ROLLED OFF THE THROTTLE AND VERIFIED THAT THE COLLECTIVE WAS LOWERED. THE HELICOPTER CONTINUED TO SHAKE WITH THE BLADES STRIKING THE GROUND. THE SADDLE FUEL TANK SEPARATED FROM THE HELICOPTER AND A FIRE WAS INITIATED. THE PILOT WAS ABLE TO EVACUATE THE HELICOPTER PRIOR TO ITS BEING CONSUMED BY FIRE. POST ACCIDENT INSPECTION OF HELICOPTER AND ITS COMPONENTS NOT DESTROYED IN THE FIRE FAILED TO REVEAL ANY FAILURE/MALFUNCTION WHICH WOULD HAVE RESULTED IN THE ACCIDENT.
Probable cause
THE PILOT'S IMPROPER USE OF COLLECTIVE IN RECOVERING FROM A LOSS OF CONTROL DUE TO GROUND RESONANCE.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI93LA159
- Event ID
- 20001211X12346
- Case number
- CHI93LA159
- 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: 766bb37b4470bf82ac9138c334071ccb8103945a112b86f73a7774ade436e938; retrieved 2026-09-21T22:58:03.019Z.