FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

MIA03FA043 · Cessna 172P

18 Jan 2003 · Edgewater, FL, United States

Comair Aviation Academy Cessna 172P · Accident: loss of control in flight while maneuvering

From Orlando Sanford International Airport (KSFB) to an unrecorded destination

Report a problem

Event

NTSB case
MIA03FA043
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
4 · 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 172P

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
N65906
Onboard fatalities
Unknown
Route
From Orlando Sanford International Airport (KSFB), Sanford, FLTo 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
Maneuvering
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
Loss of control in flight
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

  • Pilot in command › Aircraft control, not maintained
  • Pilot in command › Descent, not corrected

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

NTSB narrative

Two witnesses located in another airplane stated they observed N65906 in level flight, on a southerly heading, about 1,000 feet below them. N65906 then started a turn to the right and then suddenly nosed down to a near vertical attitude. The airplane was not spinning and the nose then went past the vertical to between 110 and 120 degrees. After losing about 75 percent of the altitude they observed something that appeared to be the size of a control surface separate from the airplane and the airplane began to spin. About 2 to 3 seconds later the airplane hit the ground. The outboard portion of the left wing, 10 feet in length, with the aileron still attached, was recovered approximately 150 feet to the east of the main wreckage. An outboard section of the right aileron, two feet in length, was located about 30 feet from the outboard portion of the left wing. Pieces of the left and right fiberglass wing tips were located about 800 feet east of the main wreckage along with papers from inside the airplane. The right wing remained attached to the airplane and was deformed downward and rearward. Flap actuator gear measurements indicate the flaps were in the 30 degree down position. The left wing had failed downward, and separated about 20 inches outboard of the wing strut attachment. The vertical and horizontal stabilizers, aft end of the fuselage, fractured piece of the elevator horn, fractured pieces of the control yokes, and the upper end of the right wing strut were sent to the NTSB Materials Laboratory in Washington D.C. for further examination. Visual examination of the fractured faces of the components revealed features typical of overstress separation. No evidence of fatigue cracking or corrosion damage was noted during the visual inspection. No preexisting airframe failure was found that would have led to loss of control or inflight breakup. Recorded radar data obtained from the Federal Aviation Administration (FAA), Daytona Beach Approach Control, showed the accident flight maintained 3,300 feet from 1221:45 until 1223:27. The flight was flying on a southerly heading during this time. Between 1223:32 and 1224:18, the flight maintains 3,400 feet while continuing to fly a southerly heading, and the calibrated airspeed (derived from radar groundspeed) dropped to 59 knots at 1224:15. Between 1224:22 and 1224:41, the flight maintained 3,500 feet, and the calibrated airspeed increased to 80 knots at 1224:30. At 1224:45, the flight was at 3,300 feet and at 1224:50, the flight was at 3,200 feet. Calibrated airspeed decreased to 65 knots. At 1224:55, the flight was at 3,300 feet, and the calibrated airspeed decreased to 60 knots. At 1224:59, the flight was at 3,300 feet, and the calibrated airspeed was about 58 knots. At 1225:04, the flight is at 3,200 feet and the calibrated airspeed is at 53 knots. The flight had maintained a southerly heading throughout this time. No further radar data was recorded for the accident flight. Radar data also showed that the airplane flown by the two witnesses was to the east of the accident airplane at 4,400 feet. Post mortem examination of the pilot, who was seated in the right front seat, and the left front seat passenger showed no findings which could be considered causal to the accident and toxicology studies were negative for alcohol, drugs, and carbon monoxide.

Probable cause

The pilot's inflight loss of control and the pilot's failure to recover from the resultant dive for unknown reasons which resulted in flight beyond the design stress limits of the airplane and subsequent in flight airframe breakup.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record MIA03FA043
Event ID
20030123X00096
Case number
MIA03FA043
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: 3134d056a8979a1b38d373e8b89257f221fc7d9a71754c001363b2040f3a4134; retrieved 2026-09-20T19:31:24.939Z.