Cessna 172S accident near Hermantown, MN

On October 2, 2022, a Cessna 172S (airplane) was involved in an accident near Hermantown, MN. 3 people died. Damage to the aircraft: substantial.

Date

October 2, 2022

Place

Hermantown, MN

Aircraft

Cessna 172S · Airplane

Injuries

3 fatal, 0 serious, 0 minor

Damage

Substantial

Position

46.822°N, 92.223°W

NTSB ID

20221002106032

Official records · ERA23FA001

• Public docket: reports, statements and exhibits from the investigation

Air traffic control records

• ATC - Group Chair's Factual Report: Document (PDF), on ntsb.gov
• ATC - Attachment 1 - ATC Audio Transcript: Transcript (PDF), on ntsb.gov
• ATC - Attachment 2 - Ads-B Data: Document (CSV), on ntsb.gov
• ATC - Attachment 3 - Stars Radar Data: Document (PPB), on ntsb.gov
• ATC - Attachment 5 - Facility Logs And Records: Document (PDF), on ntsb.gov

NTSB summary

HISTORY OF FLIGHT On October 1, 2022, at 2317 central daylight time, a Cessna 172S, N262TA, was substantially damaged when it was involved in an accident near Hermantown, Minnesota. The commercial pilot and two passengers sustained fatal injuries and two people occupying a house sustained minor injuries. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight. The pilot and the two passengers departed South St. Paul Municipal Airport-Richard E Fleming Field (SGS), South St. Paul, Minnesota, about 1015, and had flown to Duluth International Airport (DLH), Duluth, Minnesota, earlier that day to attend a wedding. According to airport security video, the pilot and the two passengers returned to DHL and the pilot conducted a preflight inspection of the airplane at 2246, and the passengers boarded about 2254. At 2305, the pilot contacted air traffic control and received an instrument flight rules (IFR) clearance back to SGS. A controller cleared the pilot direct to SGS and directed him to climb to 6,000 ft mean sea level (msl). The pilot was also provided a departure frequency and transponder code. The pilot then read back the wrong departure frequency and no beacon code. The controller again provided the beacon code and advised the pilot the rest of the readback was correct, but did not correct the readback of the incorrect departure frequency. The pilot was cleared to taxi to runway 09, during which time the controller informed him that the visibility was about ½-mile. The controller also advised the pilot that after he departed he may be ope

Probable cause

The pilot’s loss of airplane control due to spatial disorientation during initial climb in dark night and low instrument meteorological conditions, which resulted in a descent into terrain. Contributing to the accident was the pilot’s fatigue due to a long day of flying and personal activities.

More accidents in MN

• Jetstream BA-3100, Dec 2, 1993
• Raytheon Corporate Jets BAE 125-800A, Jul 31, 2008
• Beech King Air 100, Oct 25, 2002
• Cessna 180, Jul 12, 1987
• Cirrus Design Corp. SR22, Nov 25, 2007

Browse: Minnesota · Cessna aircraft

See it on the map

Source: NTSB aviation accident database (US government, public domain). Findings may be preliminary or later revised by the NTSB. Not a complete global record.