Cessna 182 accident near Blue Earth, Minnesota, April 3, 2017
On April 3, 2017 at about 3:00 am local time, a 1961 Cessna 182, registered N8889X, was substantially damaged in an accident during approach (VFR pattern final) near Blue Earth, Minnesota (Blue Earth Muni airport). It was a personal flight under general aviation rules (Part 91). 2 people had minor injuries; 1 other was unhurt. The weather was instrument conditions (cloud, fog or low visibility).
The NTSB's probable cause their words, unchanged
The pilot's decision to continue the night, visual flight into instrument meteorological conditions, which resulted in controlled flight into terrain while on final approach. Contributing to the accident was the pilot's improper use of an electronic flight bag.
Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- April 3, 2017 · about 3:00 am local time
- Place
- Blue Earth, Minnesota · Blue Earth Muni · map
- Type
- Accident
- Injuries
- 2 people had minor injuries; 1 other was unhurt.
- Weather
- instrument conditions (cloud, fog or low visibility)
- Aircraft
- Cessna 182 D, built 1961 · all 182s on the register
- Registration
- N8889X · no longer on the register · serial 18253289
- Damage
- Substantial damage
- Flight
- Personal flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
The pilot reported that, while approaching the destination airport in night, marginal visual meteorological conditions, he turned on the pilot-controlled runway lights. He added that he began a descent to the runway without observing the runway lights or airport and encountered "ground fog" about 200 to 300 ft above ground level (agl). He further added that he continued the descent to the runway while referencing the navigational moving map and GPS altitude on his electronic flight bag (EFB) application ForeFlight. Subsequently, while in a left turn, the airplane impacted terrain about 1 nautical mile south of the runway. The left wing, firewall, and fuselage sustained substantial damage. The pilot reported that there were no preaccident mechanical malfunctions or failures with the airplane that would have precluded normal operation. He added that, while en route, he reset his airplane-installed barometric pressure altimeter to the GPS altitude indicated on his EFB, which resulted in a "300 ft. error." An automated weather observing station, about 14 nautical miles west of the accident airport, recorded visibility at 2 1/2 statute miles, light rain, mist, and an overcast cloud ceiling at 300 ft agl.
The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.
The factual record from the NTSB's investigation tables, in plain English
What happened, in order
- VFR encounter with IMC during approach (VFR pattern final)
- Loss of visual reference during approach (VFR pattern final)
- Controlled flight into terrain or object (CFIT) during approach (VFR pattern final) defining event
The NTSB's findings
- cause Personnel issues › Action/decision › Info processing/decision › Decision making/judgment › Pilot
- cause Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Altitude › Not attained/maintained
- factor Aircraft › Aircraft systems › Indicating/recording systems › (general) › Incorrect use/operation
- Environmental issues › Conditions/weather/phenomena › Ceiling/visibility/precip › Fog › Decision related to condition
- Environmental issues › Conditions/weather/phenomena › Ceiling/visibility/precip › Below VFR minima › Decision related to condition
Pilot
- Certificate: private
- Ratings: single-engine land; instrument: airplane
- Flight time: 1,069.8 hours in all; 32.8 in this make and model; 12.1 in the last 90 days; 7 in the last 30 days; 1,069.8 as pilot in command
- Last flight review: September 9, 2016
- Medical certificate: Class 3 (with waivers/limitations)
- Seat: rgt
- Injury: minor injuries
Dual student
- Certificate: student
- Flight time: 35 hours in all; 35 in this make and model
- Medical certificate: Class 3 (without waivers/limitations)
- Seat: left
- Injury: minor injuries
Passenger
- Seat: left
- Injury: no injuries
The aircraft
- Airframe total time: 3,143.1 hours
- Last inspection: inspection type not recorded
- Maximum gross weight: 2,650 lb
- Seats: 4
- Landing gear: fixed
- Engine: Continental O-470-L (piston); 4,528 hours total
The flight
- Departed from: 21D St Paul MN at 1:30 am
- Destination: SBU Blue Earth MN
- Flight plan: none
- Runway 34, 3,400 ft by 75 ft
- A second pilot was aboard
Weather at the time
- Light: night
- Wind: from 170° at 7 knots
- Visibility: 2.5 statute miles
- Sky: overcast at 300 ft
- Temperature: 48°F (9°C), dew point 46°F (8°C)
- Altimeter: 29.80 inHg
- Observation at 3:06 am from KFRM, 14 miles away
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 2 | |||
| Passengers | 1 |
Documents from the investigation the NTSB's docket: the evidence folder behind the report
3 documents, released by the NTSB on May 30, 2017. View them here, or download them; the NTSB redacts some personal details before release, and this site shows the NTSB's own titles rather than its file names.
| # | Document | What it is | |
|---|---|---|---|
| 1 | Pilot/operator Aircraft Accident Report, NTSB Form 6120.1 | PDF, 9 pages | View Download |
| 2 | Record of Conversation (Pilot) | PDF, 1 page | View Download |
| 3 | Accident Photo (Courtesy of FAA) | PDF, 1 page | View Download |
The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.
Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text never names anyone involved. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.