FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN21FA220 · Cessna 182 H

17 May 2021 · St. Louis, MI, United States

Gateway Air Service Cessna 182 H · Accident: collision with terrain/object (non-CFIT) en route

From Romeo State Airport (D98) to Clare Municipal Airport (48D)

Report a problem

Event

NTSB case
CEN21FA220
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
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

Cessna 182 H

Aircraft type
Cessna 182
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
N2430X
Onboard fatalities
Unknown
Route
From Romeo State Airport (D98), Romeo, MITo Clare Municipal Airport (48D), Clare, MI
Aircraft age
About 56 years (built 1965)
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
Defining eventThe 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
Collision with terrain/object (non-CFIT)
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

  • Personnel issues › Psychological

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

The pilot was conducting a low-altitude pipeline patrol flight in day visual meteorological conditions when the airplane collided with a radio tower guy wire. According to radar data, during the final 4.5 minutes of the flight, the airplane’s altitude was between 475 and 800 ft above ground level (agl). The airplane’s ground track was offset to the right of the pipeline until about the final minute of the flight, at which point the airplane crossed over the pipeline and continued about 1,000 to 1,250 ft to the left of the pipeline. The operator reported that the airplane should be flown to the right of the pipeline to ensure that the pilot, who is seated in the left cockpit seat, can maintain an unobstructed view of the pipeline during the patrol flight.

The airplane continued northwest toward the radio tower. About 15 seconds before the accident, the airplane was about 0.65 miles southeast of the tower in a shallow right turn when it entered a climb from 475 ft agl. At the final radar return, about 600 ft east-southeast of the tower, the airplane’s altitude, calibrated airspeed, and climb rate were about 1,370 ft msl, 104 knots, and 1,575 ft per minute, respectively. The airplane’s final altitude was 370 ft below the top of the radio tower and its ground track was toward the guy wires located on the northeast side of the radio tower. Based on the airplane’s ground track and rapidly increasing climb rate, the pilot was likely trying to avoid the tower guy wires during the final moments of the flight.

The airplane’s left wing separated from the fuselage at the wing root when it collided with a support guy wire attached to the northeast side of the radio tower. The airplane then impacted a dirt field about 0.3 mile northwest of the radio tower where a postimpact fire destroyed most of the airplane. Postaccident examination of the airplane wreckage did not reveal any evidence of a mechanical malfunction or failure that would have prevented normal operation of the airplane before it collided with the tower guy wire.

Two individuals reported that the pilot posted a Snapchat video shortly before the accident. The Snapchat video reportedly depicted the terrain ahead of the airplane while it was 5 to 10 miles southeast of the accident site. Although the video was automatically deleted from the Snapchat platform 24 hours after the accident, it reportedly did not include the final moments of the flight. One of the individuals provided a screenshot of the Snapchat application’s map that showed the approximate location of where the pilot posted the video. When compared to the airplane’s recorded radar ground track, the location of the pilot’s Snapchat post was about 1.5 miles southeast of the radio tower, and likely was posted about 35 seconds before the accident. The airplane’s ground track was already left of the pipeline when the pilot posted the Snapchat video. Based on the known information, it is likely the pilot was distracted while he used his mobile device in the minutes before the accident and did not maintain an adequate visual lookout to ensure a safe flight path to avoid the radio tower and its guy wires.

Probable cause

The pilot’s failure to maintain adequate visual lookout to ensure clearance from the radio tower and its guy wires. Contributing to the accident was the pilot’s unnecessary use of his mobile device during the flight, which diminished his attention/monitoring of the airplane’s flight path.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN21FA220
Event ID
20210517103091
Case number
CEN21FA220
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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, coordinates, cause areas. 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: a84db8a7bdc3811ed4907c04b34c9a04c4f8f27d7c39174c9703c9f0f99e6be8; retrieved 2026-09-15T07:28:22.108Z.