Cessna 172 accident near Orlando, Florida, August 16, 2024
On August 16, 2024 at about 7:17 pm local time, a 1975 Cessna 172, registered N61859, was substantially damaged in an accident during landing near Orlando, Florida (Exec airport). It was an instructional flight under general aviation rules (Part 91). No one was hurt; 2 people were on board or involved. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
The student pilot's failure to maintain directional control during while landing with a crosswind. Contributing was the instructor’s delayed remedial action.
Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- August 16, 2024 · about 7:17 pm local time
- Place
- Orlando, Florida · Exec · map
- Type
- Accident
- Injuries
- No one was hurt; 2 people were on board or involved.
- Weather
- visual conditions (good weather)
- Aircraft
- Cessna 172 M, built 1975 · all 172s on the register
- Registration
- N61859 · registry record · serial 17264849
- Damage
- Substantial damage
- Flight
- Instructional flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
According to the flight instructor, the wind was gusting significantly during the practice short field landing with the student pilot. He described that the student pilot made a normal approach, but as they got over the runway and attempted to land and entered ground effect, the airplane ballooned and turned sideways, which was exacerbated by the winds. The student pilot added power but did not input sufficient rudder control to straighten the airplane’s flight track. The airplane continued to float as the student increased engine power rapidly, then the student “froze” as the airplane began to turn further sideways over the grass. The flight instructor took control of the airplane, added full power, and attempted a go around but was unable to regain directional control and stop the descent. The airplane landed hard in a marshy area off the side of the runway, substantially damaging the wings and fuselage. The flight instructor reported that there were no preimpact mechanical malfunctions or failures of the airplane that would have precluded normal operation.
The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.
The factual record from the NTSB's investigation tables, in plain English
What happened, in order
- Loss of control in flight during landing defining event
The NTSB's findings
- Personnel issues › Action/decision › Action › Delayed action › Instructor/check pilot
- Environmental issues › Conditions/weather/phenomena › Wind › Crosswind › Response/compensation
- Personnel issues › Task performance › Use of equip/info › Aircraft control › Student/instructed pilot
- Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Directional control › Not attained/maintained
Flight instructor
- Certificate: flight instructor, commercial pilot, private
- Ratings: multi-engine land; single-engine land; instructor: airplane multi-engine; instructor: airplane single-engine; instructor: instrument airplane; instrument: airplane
- Flight time: 800 hours in all; 531 in this make and model; 110 in the last 90 days; 38 in the last 30 days; 719 as pilot in command; 517 on instruments
- Last flight review: September 11, 2023
- Medical certificate: Class 1 (with waivers/limitations)
- Seat: rgt
- Injury: no injuries
Dual student
- Certificate: student
- Flight time: 85 hours in all; 84 in this make and model; 7 in the last 90 days; 6 in the last 30 days; 11 as pilot in command
- Medical certificate: Class 1 (with waivers/limitations)
- Seat: left
- Injury: no injuries
The aircraft
- Airframe total time: 11,504 hours
- Last inspection: 100-hour inspection, July 2, 2024; 92 hours since
- Maximum gross weight: 2,300 lb
- Seats: 4
- Landing gear: fixed
- Engine: Lycoming O-320-E2D (piston); 487 hours total
- Operator: Jprg Aviation INC
The flight
- Flight plan: none
- Runway 7, 6,004 ft by 150 ft
- A second pilot was aboard
Weather at the time
- Light: daylight
- Wind: from 060° at 9 knots, gusting 17
- Visibility: 10 statute miles
- Sky: scat at 7,500 ft
- Temperature: 90°F (32°C), dew point 66°F (19°C)
- Altimeter: 30.02 inHg
- Observation at 2:53 pm from ORL
Weather report (METAR): KORL 161853Z 06009G17KT 030V090 10SM SCT075 32/19 A3002 RMK AO1 SLP167 T03220189
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 2 |
Photographs from the investigation 4 pictures from the NTSB's docket, as the NTSB released them
Photograph 1 – Airplane as its being recovered.
Photograph 2 – Fuselage and engine compartment damage.
Photograph 3 – Left wingtip damage.
Photograph 4 – Overall view of airplane after recovery.The NTSB's photographs with the NTSB's captions, at screen size. Open a picture to see it full size or to report one that should not be shown.
Documents from the investigation the NTSB's docket: the evidence folder behind the report
2 documents, released by the NTSB on September 27, 2024. View them here, or download them; the NTSB redacts some personal details before release, and this site shows the NTSB's own titles rather than its file names.
| # | Document | What it is | |
|---|---|---|---|
| 1 | Pilot/operator Aircraft Accident Report, NTSB Form 6120.1 | PDF, 11 pages | View Download |
| 2 | Investigative Photographs | PDF, 5 pages · our copy | View Download |
The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.
Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text never names anyone involved. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.