CHI91DTG01 · Cessna 172P
Flight Training Cessna 172P · Accident: in flight encounter with weather
From Bismarck Municipal Airport (BIS) to Hector International Airport (FAR)
Event
- NTSB case
- CHI91DTG01
- 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
- Unknown
Cessna 172P
- Aircraft type
- Cessna 172
- 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
- N5478K
- Operator
- Flight Training
- Onboard fatalities
- Unknown
- Route
- From Bismarck Municipal Airport (BIS), BISMARK, NDTo Hector International Airport (FAR), Fargo, ND
- 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
- Unknown
- 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 encounter with weather
- 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
- Visual flight rules (VFR) flight into instrument meteorological conditions (IMC)
- 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 › Spatial disorientation
Approximate · Estimated position: the centre of Bismarck, ND, the place the record names. Not the accident site.
NTSB narrative
THE NON-INSTRUMENT RATED PILOT HAD ONLY THREE HOURS OF NIGHT TIME AND DID NOT OBTAIN A PREFLIGHT WEATHER BRIEF. HE ELECTED TO TAKE OFF AT 0050 AND MAKE THE RETURN FLIGHT HOME IN ORDER TO MAKE A MILITARY RESERVE COMMITMENT. THE TEMPERATURE WAS 58 DEGREES F, DEW POINT 56 DEGREES F. THE PILOT TOLD A FRIEND AT THE AIRPORT THAT HE WAS GOING TO FOLLOW THE INTERSTATE HIGHWAY. THE WRECKAGE WAS FOUND THE FOLLOWING MORNING EIGHT MILES NORTHEAST OF THE AIRPORT, AND THREE QUARTERS OF A MILE NORTH OF THE INTERSTATE. A STATE TROOPER ON DUTY AT THE TIME OF THE ACCIDENT REPORTED THAT FOG WAS FORMING AT THE TIME OF THE ACCIDENT, AND THAT THE ACCIDENT SITE WAS AN AREA WHERE FOG IS VERY COMMON.
Probable cause
SPATIAL DISORIENTATION. FACTORS RELATED TO THE ACCIDENT ARE FAILURE TO OBTAIN A PREFLIGHT WEATHER BRIEF, VRF FLIGHT INTO IMC CONDITIONS AND LACK OF TOTAL EXPERIENCE.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI91DTG01
- Event ID
- 20001212X17207
- Case number
- CHI91DTG01
- 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: 41162b5a870cbfaa0a6c235b9b60cc2eccca7e6cc7db1f1394116480ad361e6f; retrieved 2026-09-21T01:47:35.060Z.