CHI04LA173 · Piper PA-28-161
Piper PA-28-161 · Accident: in flight collision with terrain/water en route
From Crystal Airport (MIC) to Grand Forks International Airport (GFK)
Event
- NTSB case
- CHI04LA173
- 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
- Unknown
- 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
Piper PA-28-161
- Aircraft type
- Piper PA-28
- 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
- N248ND
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Crystal Airport (MIC), Crystal, MNTo Grand Forks International Airport (GFK), Grand Forks, 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
- 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
- In flight collision with terrain/water
- 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 › Altitude, not maintained
- Pilot in command › Planning/decision, improper
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The airplane was destroyed when it impacted terrain during cruise flight at 0135 central daylight time. The private pilot was working on his commercial and instrument flight ratings. The flight was a night cross-country flight which required landings at three different airports with one segment of the flight consisting of a straight-line distance of at least 250 nautical miles between airports. The pilot reported that on July 6th he woke up at 0800 and that he went to bed at 0200 on July 7th. On July 7th, he slept until 0730-0800. The pilot reported that he departed Grand Forks (GFK), North Dakota, at 1815. He flew to Airlake Airport (LVN), Minneapolis, Minnesota, on the first leg of his cross-country flight and arrived there at 2030. He departed LVN and continued on the second leg of the flight plan. He arrived at Crystal Airport (MIC) at 2130. He had the airplane fueled with 24 gallons of fuel. He met with a friend and they went to eat at a restaurant where he had a meal. He returned to the airport and departed at 2355. He reported that he climbed to 4,500 feet mean sea level (msl) and contacted flight service about 0030 to open his flight plan back to GFK. The pilot flew for about 1.5 hours on a northwesterly heading. The pilot reported that he remembered seeing Detroit Lakes, Minnesota, in the distance, but did not remember anything else about the flight. He reported that the next thing he remembered was when he opened his eyes and realized that he was in a corn field and that the airplane had crashed. He was unable to move, but he yelled for help when rescue personnel arrived at the accident site. Radar data indicated that N248ND was flying on a northwesterly heading. The airplane's altitude was approximately 4,200 - 4,800 feet msl and the ground speed was about 110 knots. The airplane proceeded on course until about 0126. The radar data indicated that the airplane entered descending turns to the left. The airplane completed 6 1/2 turns before it was lost from radar. The last radar return recorded was at 0133. It indicated the airplane's altitude was about 1,900 feet msl (less than 400 feet agl). The pilot reported to the NTSB the following information: "First, I should not have taken off thinking that I might get tired. I should have requested flight following to keep my attention. Possibly [I] should have recognized symptoms of fatigue and possibly state of consciousness, and landed before losing consciousness." The post accident inspection of the airplane revealed no preexisting anomalies that could be associated with a pre-impact condition.
Probable cause
The pilot's failure to get the proper rest prior to the night cross country flight and the pilot's failure to maintain altitude. Contributing factors to the accident were fatigue as a result of inadequate sleep, conditions conducive to fatigue, and night.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI04LA173
- Event ID
- 20040715X00984
- Case number
- CHI04LA173
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
Source notes (5)
- 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, coordinates. 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: 22873ccc39d40a2b6f91742591857fc138c9796341e2b51299d75e103ffd7509; retrieved 2026-09-21T09:15:45.682Z.
- Corrected after a review of the NTSB narrative, which states these values explicitly: damage. The narrative states "The airplane was destroyed when it impacted terrain during cruise flight".