ASN Wikibase Occurrence # 285617
This information is added by users of ASN. Neither ASN nor the Flight Safety Foundation are responsible for the completeness or correctness of this information.
If you feel this information is incomplete or incorrect, you can submit corrected information.
| Date: | Saturday 1 October 2022 |
| Time: | 23:17 |
| Type: |  Cessna 172S Skyhawk SP |
| Owner/operator: | Svetfur Aviation LLC |
| Registration: | N262TA |
| MSN: | 172S9262 |
| Year of manufacture: | 2002 |
| Fatalities: | Fatalities: 3 / Occupants: 3 |
| Aircraft damage: | Destroyed |
| Category: | Accident |
| Location: | Hermantown, MN -
 United States of America
|
| Phase: | En route |
| Nature: | Private |
| Departure airport: | Duluth International Airport, MN (DLH/KDLH) |
| South St Paul Municipal Richard E Fleming field, MN (KSGS) | |
| Investigating agency: | NTSB |
| Confidence Rating: |  Information verified through data from accident investigation authorities |
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. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight.
According to a witness, the pilot and two passengers, all friends, departed South St Paul Municipal Airport-Richard E Fleming Field (SGS), South St Paul, Minnesota, about 1015 and flew about 130 nautical miles to Duluth International Airport (DLH), Duluth, Minnesota. Shortly after arrival at DLH, the group attended a wedding and reception. About 12 hours after arriving, the pilot and passengers arrived back at the airplane. According to the fixed-base operator, no fueling or maintenance were requested.
The pilot requested an instrument flight rules (IFR) clearance from the air traffic controller and was subsequently cleared to SGS via direct, with a climb to 6,000 ft on departure and was issued a departure frequency and beacon code; the frequency was read back incorrectly by the pilot and not corrected by the air traffic controller.
The pilot reported that he was ready for taxi and the controller instructed the pilot to taxi to the runway. The controller reported that there was about 1/2-mile visibility and subsequently advised cloud bases were reported at 250 ft agl. The pilot reported holding short of runway 9 and ready for takeoff. The controller cleared the airplane for takeoff with a right turn direct to SGS on departure. The controller also reported that the winds were from 090° at 14 knots gusting to 18 knots, and the runway visual range was greater than 6,000 ft, which the pilot acknowledged.
Preliminary Automatic Dependent Surveillance–Broadcast (ADS–B) data indicated the flight departed DLH runway 09 at 2312, then turned on a southerly track while climbing to about 1,750 ft mean sea level (msl) about 1 mile south of the departure runway. The airplane entered a tight teardrop turn to the left while climbing through 2,000 ft msl, then continued the turn 360° until it was on a track of about 270° at 2,800 ft msl, then began a descent.
The controller attempted to contact the pilot on departure frequency with no response. He then transmitted on the tower frequency and instructed the pilot to contact departure. The pilot responded by saying “contacting departure two tango alpha.” Several seconds later, while the airplane continued to descend in a left turn with increasing ground speed, the controller informed the pilot that he observed the airplane descending and asked him to confirm that he was climbing. There was no response and no further communication from the pilot.
Preliminary weather information was obtained from DLH, which was located about 1 mile north of the accident site at an elevation of 1,428 ft. At 2255, the recorded weather at DLH included wind from 080° magnetic at 10 knots gusting to 19 knots, 5 statute miles visibility, mist, ceiling overcast at 200 ft agl, temperature 9° C, dew point temperature 8° C, and altimeter 30.38 inches of mercury (inHg).
The airplane impacted the front roof of a two-story house at an elevation of 1,400 ft, and on a track of about 210°. It passed through two upstairs bedrooms, and then struck terrain before coming to rest inverted between a vehicle and a detached garage. There was no postcrash fire. The wreckage path was oriented on a magnetic heading of 202° and was about 100 ft in length. All major components of the airplane were located within the area.
The left wing was impact separated from the fuselage and was discovered on the front yard of the house. The empennage was separated from the fuselage at the leading edge of the horizontal stabilizer and was discovered against the front door of the detached garage. The remaining fuselage, cockpit and right wing were inverted and wedged between the garage and a vehicle. No visible fuel was present at the scene and there was no associated fuel blight discovered on the trees or surrounding grass; however, fire rescue personnel reported a strong fuel odor during their recovery operations.
Control continuity was confirmed from all flight control surfaces through breaks in the flight control cables that were consistent with tensile overload.
The engine was impact separated from the firewall and remained upright adjacent to the fuselage. It was relatively intact and there was no damage to the aft accessory section of the engine. The propeller flange was sheared off at the crankshaft and the damage was consistent with rotation of the crankshaft at the time of impact. The propeller was found in the wreckage next to the engine and exhibited chordwise scraping and leading-edge gouges. Both propeller blades were bent aft mid span and the propeller spinner was crushed and twisted.
The engine spark plugs were removed and examined. They had minimal wear when compared to the Champion Check-A-Plug chart and did not display any evidence of carbon or lead fouling. Both left and right magnetos were intact. Both units were operated manually with a drill socket and all posts produced a spark with no anomalous behavior noted. Residual fuel was discovered in the fuel pump and fuel odor was noticed in the flow divider.
The engine was rotated via the accessory section. Thumb compression and suction was attained on all cylinders and crankshaft continuity was confirmed. All valves, pushrods and springs operated normally. The crankshaft rotation was smooth, with no noticeable abnormal noise or friction noted.
The wreckage was retained for further examination.
Sources:
https://www.mprnews.org/story/2022/10/02/3-people-dead-in-hermantown-minn-small-plane-crash
https://www.duluthnewstribune.com/news/local/3-people-killed-in-light-plane-crash-near-duluth-airport
https://archive.liveatc.net/kdlh/KDLH1-Oct-02-2022-0400Z.mp3 (incident @ 14:30)
https://registry.faa.gov/AircraftInquiry/Search/NNumberResult?nNumberTxt=262TA
https://flightaware.com/live/flight/N262TA/history/20221002/0355Z/KDLH/KSGS
https://cdn.jetphotos.com/full/6/57083_1632633079.jpg (photo)
History of this aircraft
Other occurrences involving this aircraft
| 14 February 2004 | N262TA | The Flight School of Palm Springs | 0 | Riverside, CA | |
sub |
Location
Media:
NTSB is investigating the Oct. 1, 2022, crash of a Cessna C172 near Hermantown, Minnesota.
— NTSB Newsroom (@NTSB_Newsroom) October 2, 2022
Here are some of the first photos from the plane crash in Hermantown. Police have now confirmed that 3 people have died in the crash. 2 males, and 1 female all from the Twin Cities area. @robbcoles is on the scene gathering more information. pic.twitter.com/os2dPOtYYF
— Natalie Grant (@naniigrant) October 2, 2022
Revision history:
| Date/time | Contributor | Updates |
|---|---|---|
| 02-Oct-2022 12:25 | gerard57 | Added |
| 02-Oct-2022 13:07 | RobertMB | Updated [Location, Source, Narrative] |
| 02-Oct-2022 13:26 | RobertMB | Updated [Time, Aircraft type, Registration, Cn, Operator, Total fatalities, Departure airport, Destination airport, Source, Narrative] |
| 02-Oct-2022 13:48 | Captain Adam | Updated [Total fatalities, Total occupants, Source, Narrative] |
| 02-Oct-2022 18:47 | RobertMB | Updated [Location, Source, Embed code, Narrative] |
| 02-Oct-2022 18:54 | RobertMB | Updated [Embed code, Narrative] |
| 02-Oct-2022 22:19 | Captain Adam | Updated [Location, Source, Embed code, Narrative, Category] |
| 03-Oct-2022 01:54 | johnwg | Updated [Time, Source, Narrative, Category] |
| 03-Oct-2022 05:48 | shane | Updated [Source, Embed code] |
| 03-Oct-2022 12:25 | johnwg | Updated [Time, Category] |
| 03-Oct-2022 17:23 | Captain Adam | Updated [Location, Source, Narrative] |
| 19-Oct-2022 19:38 | Captain Adam | Updated [Time, Narrative] |
Corrections or additions? ... Edit this accident description
The Aviation Safety Network is an exclusive service provided by:
Quick Links:
| ASN Home | Send Correction / Feedback |
| FSF Home | Disclaimer | Copyright |
| Contact Us | Privacy Policy |
| Press / Media |
CONNECT WITH US:
©2024 Flight Safety Foundation