ERA23LA210 · Piper PA-30
Piper PA-30 · Accident: landing gear not configured
From Orlando Sanford International Airport (SFB) to an unrecorded destination
Event
- NTSB case
- ERA23LA210
- 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
- 0 · all aircraft and ground
- Ground fatalities
- 0
- 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
Piper PA-30
- Aircraft type
- Piper PA-30
- 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
- N751WW
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Orlando Sanford International Airport (SFB), Orlando, FLTo not recorded
- Aircraft age
- About 56 years (built 1967)
- 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
- Landing · flare/touchdown
- 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
- Landing gear not configured
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Substantial
Cause areas
- Aircraft › Aircraft systems
- Personnel issues › Action/decision
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot reported that as he entered the airport environment for landing, while on about a 3-mile final approach, the air traffic control tower controller instructed him to perform a left 360° turn. The pilot completed the turn, and the controller cleared him to continue the approach and land. As the pilot continued the final approach to land, the sun was in his eyes, and he noticed two objects on the runway. He inquired the tower about what was on the runway, but before the controller could respond, he identified the objects as two F-18 fighter aircraft departing. Subsequently, during the landing flare he heard “gear gear gear” over the radio and then touched down with the landing gear retracted. The airplane skidded to a stop on the runway. The fuselage sustained substantial damage. The pilot reported that he omitted completing his mental landing checklist of “gear, propeller, mixture, pumps, speed, stable.” The pilot reported that there were no preimpact mechanical malfunctions or failures with the airplane that would have precluded normal operation.
Probable cause
The pilot’s failure to extend the landing gear before landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA23LA210
- Event ID
- 20230427107155
- Case number
- ERA23LA210
- 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, 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: 94d5869db160e015f4d91eb17f442e3bd07198e7db6b89009389649cf1190cea; retrieved 2026-09-16T17:33:05.770Z.