CHI98LA021 · Schweizer 269C
Schweizer 269C · Accident: in flight collision with object on approach
From Park Rapids Municipal Airport Konshok Field (PKD) to Grand Forks International Airport (GFK)
Event
- NTSB case
- CHI98LA021
- 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
- N557DC
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Park Rapids Municipal Airport Konshok Field (PKD), Park Rapids, MNTo Grand Forks International Airport (GFK)
- 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
- Approach
- 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
- In flight collision with object
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Wire, transmission
- 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 › Preflight planning/preparation, inadequate
- Pilot in command › Visual lookout, not possible
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot stated he knew he was low on fuel during the last leg of a cross country flight. The low fuel light illuminated when he was 9.5 miles from the destination airport. The pilot elected to make a precautionary landing. The light went off during the landing descent. The pilot continued the descent at which time he felt a yaw to the right. Suspecting an engine failure, he initiated a 'hovering autorotation' only to discover he still had engine power. He reported he regained control of the helicopter and continued the landing. It was later determined that the helicopter contacted an electrical wire which ran across a nearby road.
Probable cause
the pilot's inadequate preflight planning which resulted in a low fuel state, and his inability to see the wire which the helicopter contacted. Factors associated to the accident were the precautionary landing, the dark night conditions, and the wire which was contacted.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI98LA021
- Event ID
- 20001208X08979
- Case number
- CHI98LA021
- 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 1997-10-15.
- API snapshot SHA-256: 33f06aba32426ace1e27e08b9ab763372ba1b560353bf4d004bb2bc572d37382; retrieved 2026-09-22T18:21:29.265Z.