Cessna 750 accident near Fort Myers, Florida, May 9, 2026
On May 9, 2026 at about 2:14 pm local time, a 1998 Cessna 750, registered N119RM, was substantially damaged in an accident during landing (flare/touchdown) near Fort Myers, Florida (Page Fld airport). It was a positioning 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 NTSB has not yet published a probable cause for this accident. Investigations usually take one to two years; this page updates when the final report is released.
Source: NTSB aviation accident database, copy made November 2, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- May 9, 2026 · about 2:14 pm local time · cases in 2026
- Place
- Fort Myers, Florida · Page Fld · cases near this airport · map
- Type
- Accident
- Injuries
- No one was hurt; 2 people were on board or involved.
- Weather
- visual conditions (good weather)
- Aircraft
- Cessna 750, built 1998 · all 750s on the register
- Registration
- N119RM · registry record · serial 750-0051
- Damage
- Substantial damage
- Flight
- Positioning flight · general aviation rules (Part 91)
The NTSB's narrative preliminary · quoted from the NTSB record
On May 9, 2026, at 1014 eastern daylight time, a Cessna 750 airplane, N119RM, was substantially damaged when it was involved in an accident near Fort Myers, Florida. The captain and first officer were not injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 positioning flight. The first officer reported that on a previous flight in the accident airplane the crew had received multiple crew alerting system (CAS) messages which included a master caution (Stab Bleed Leak) and amber caution (Tail Cone Door Open) which the captain reported to maintenance. During the accident flight, on initial climb, the crew again received the CAS messages for the same master caution and amber caution repeatedly. The captain instructed the first officer to pull the audio warning circuit breaker once cruise altitude was reached, which the first officer accomplished. During approach to the airport, the first officer reported that the captain was instructing him throughout the approach. The first officer could not recall if he verbally called for the before landing checklist. The captain reported that he had begun the before landing checklist at the final approach fix but was interrupted when air traffic control issued them their landing clearance along with the master caution turning on and off. The captain reported that he did not go back over the before landing checklist after the interruption nor verbally called the checklist complete. Both crew members reported that the airplane landed with the landing gear retracted and the first officer reported that after the airplane came to a stop the captain selected the landing gear handle to the down position. A preliminary review of surveillance footage from the airport showed the airplane approaching the runway with the landing gear in the retracted position. The airplane subsequently touched down with the landing gear in the retracted position and slid to a stop on the runway. About 6 seconds after the airplane came to a stop the nose landing gear was observed beginning to deploy. A review of postaccident photographs showed that the airplane sustained substantial damage to the fuselage. The airplane was retained for further examination.
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
- Landing gear not configured during landing (flare/touchdown) defining event
The aircraft
- Airframe total time: 9,481.1 hours
- Last inspection: type not recorded, April 19, 2026; 235 hours since
- Maximum gross weight: 35,700 lb
- Seats: 10
- Landing gear: retractable
- Operator: Hera Flight, LLC
The flight
- Departed from: FLL Fort Lauderdale FL at 1:49 pm
- Flight plan: IFR
- Runway 23, 6,406 ft by 150 ft
- A second pilot was aboard
Weather at the time
- Light: daylight
- Visibility: 10 statute miles
- Sky: clear
- Temperature: 84°F (29°C), dew point 70°F (21°C)
- Altimeter: 29.94 inHg
- Observation at 10:00 am from FMY
Weather report (METAR): METAR KFMY 091353Z VRB03KT 10SM CLR 29/21 A2994 RMK AO2 SLP142 T02890206
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 2 |
Documents from the investigation the NTSB's docket: the evidence folder behind the report
The NTSB has not released the docket for this case yet. The docket, the folder of records gathered during an investigation (maintenance records, photographs, witness statements, examinations), is usually released when the investigation is nearly complete, and the list here is refreshed when it appears. Check at the NTSB.
Connections how this case links to the rest of the register
- N119RM on the register today · the tail number may have moved to another aircraft since
- Cessna 750 Citation X 288 registered today · the model family and its accident history
- Cessna 72,672 aircraft on the register
- Page Field · nearest airport
- Fort Lauderdale/Hollywood International · departed from
- Accidents and incidents in Florida 6,111 since 1982 · 982 in the last ten years
- Florida 21,718 aircraft registered
The whole map of how records connect · these connections as data: /graph/accident/ERA26LA206.json.
The bigger picture in Aviation Analytics: accidents over time since 1982, by model, by phase of flight and conditions, by place and on the map.
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 does not name anyone involved, its policy at this time. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.
