FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CHI03FA284 · Cessna 172S

22 Aug 2003 · Lake Elmo, MN, United States

Wings Cessna 172S and Piper PA-28-181 · Accident: midair collision en route

Report a problem

Event

NTSB case
CHI03FA284
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
3 · 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

Aircraft 1 · Cessna 172S

Aircraft type
Cessna 172
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
N53033
Operator
Wings
Onboard fatalities
Unknown
Route
From Saint Paul Downtown Holman Field (STP), St. Paul, MNTo not recorded
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
Midair collision
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Destroyed

Aircraft 2 · Piper PA-28-181

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
N38416
Operator
Unknown
Onboard fatalities
Unknown
Route
From South St Paul Municipal Airport/Richard E Fleming Field (SGS), South St. Paul, MNTo BFW · Silver Bay, MN
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
Midair collision
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

  • Pilots of both aircraft › Clearance, not maintained
  • Pilots of both aircraft › Visual lookout, inadequate

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

NTSB narrative

The Cessna and Piper airplanes were destroyed when they impacted terrain after a mid-air collision. Both the Cessna and Piper aircraft were flying beneath the positively controlled Class B airspace of the Minneapolis-St. Paul International Airport. Both airplanes were operating under visual flight rules, and both airplanes were transmitting the 1200 VFR beacon code on their respective transponders. Neither airplane was required to be in radio contact with air traffic control. The student pilot in the Cessna who survived the accident reported that the CFI let him take the flight controls while they were flying straight and level. He reported that he was flying the airplane and was looking straight ahead, trying to maintain straight and level flight. He reported that the CFI put her hand on the throttle and started explaining a climb procedure. He reported that while the CFI was explaining the climb procedure, the airplane was hit by another airplane on the right side. He reported that he never saw the other airplane before the impact and that he didn't think the CFI saw it either. He reported that the CFI did not grab the controls or make any "violent maneuvers" prior to the impact. Radar data indicated that the Cessna departed Downtown St. Paul Airport (STP) at approximately 1719 to the northwest and turned right to an easterly heading, paralleling interstate highway I-94 to the east. The Cessna climbed to approximately 2,300-2,400 feet pressure altitude about 4 minutes after takeoff and remained at that altitude until impact, approximately 2 minutes later. The Cessna was traveling approximately 98 knots average ground speed during the 2 minutes prior to impact. The Piper departed South St. Paul Municipal Airport (SGS) at approximately 1719. Approximately 4 minutes after takeoff, the Piper turned to the northeast on a heading of about 027 degrees. The Piper climbed from about 1,900 feet pressure altitude to about 2,300 feet pressure altitude during the 2 minutes prior to impact. The relative bearing between the Piper and the Cessna was about 60 degrees. The radar data indicated the Piper was traveling at approximately 107 knots average ground speed during the 2 minutes prior to impact. Approximately 36 inches of the Cessna's outboard right wing structure was found lodged in the wing root of the Piper's left wing, and was located with the main wreckage of the Piper. The Piper's left wing exhibited a span-wise crease about five feet long in the lower wing skins forward of the flap. The Cessna's right wing leading edge had two distinct dents that were spaced a similar distance apart as the Piper's wing tie-down ring and jack pad. The aft left side of the Piper's fuselage in the vicinity of the registration number exhibited black, rubber-like transfer marks. The right tire from the Cessna's main landing gear had white scuff marks on the right side of the tire.

Probable cause

Both pilots failed to maintain adequate visual lookout and did not maintain clearance from the other aircraft.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CHI03FA284
Event ID
20030826X01396
Case number
CHI03FA284
Dataset
historical-pre2008
Source SHA-256
89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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. 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: 5f4e96f007cf0ae8abb7f2f6ba2000b1a2e0d94df5b20435be70f9706406dfdf; retrieved 2026-09-20T18:59:07.678Z.