ERA25LA166 · Cessna 182 P
Cessna 182 P · Accident: abnormal runway contact during landing
From Cannon Creek Airpark (15FL) to Lakeland Linder International Airport (LAL)
Event
- NTSB case
- ERA25LA166
- 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
- Ongoing
- 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
Cessna 182 P
- Aircraft type
- Cessna 182
- 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
- N1910M
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Cannon Creek Airpark (15FL), Lake City, FLTo Lakeland Linder International Airport (LAL), Lakeland, FL
- Aircraft age
- About 50 years (built 1975)
- 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
- Abnormal runway contact
- 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
No findings designated as a cause are recorded in the NTSB data yet.
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
On April 3, 2025, about 1222 eastern daylight time, a Cessna 182P, N1910M, was substantially damaged when it was involved in an accident near Sanford, Florida. The commercial pilot received minor injuries. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight. According to the pilot, while holding after several unsuccessful attempts to land at Lakeland Linder International Airport (LAL), Lakeland, Florida, he became disoriented and uncertain of his location. The pilot radioed an air traffic controller and requested assistance. The pilot stated that he was advised to switch frequencies and shortly thereafter, he was asked to “Ident,” but the controller could not locate the pilot’s position. The pilot was then advised to squawk 7700 on his transponder. The pilot became concerned about the airplane’s remaining fuel quantity, noticed an airport to his left side, later determined to be Orlando Sanford International Airport (SFB), Orlando, Florida, and elected to land. The pilot attempted a landing on runway 36, where the airplane bounced, and the pilot performed a go-around. The pilot then circled the airport at a low altitude before attempting a landing on runway 9L. During the second landing attempt, the pilot stated that a gust of wind caused the airplane to drop “hard” on the nose, subsequently, the nose gear collapsed. Witnesses at SFB reported observing the airplane flying low and “uncoordinated” over the airport. Surveillance video showed the airplane approaching from the west side of runway 36 at about a 45° angle past the threshold before the airplane bounced and then began a go-around. An additional video showed the airplane flying low and perpendicular to runway 9L at tree top height before making a left banking turn and contacting the runway in a nose down attitude. The airplane sustained substantial damage to the lower fuselage and engine mounts. The wreckage was retained for further examination.
Verbatim NTSB factual narrative from the NTSB dataset
Sources
NTSB record ERA25LA166
- Event ID
- 20250403199960
- Case number
- ERA25LA166
- 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, 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: 81a0a9acb25982c3ce8a23995ed212e7bd32767223377a1305fa47c797189711; retrieved 2026-09-16T19:47:34.234Z.