FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN25LA201 · Lancair 235

7 Jun 2025 · Pawhuska, OK, United States

Lancair 235 · Accident: landing gear not configured

From Independence Municipal Airport (IDP) to Independence Municipal Airport (IDP)

Report a problem

Event

NTSB case
CEN25LA201
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
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

Lancair 235

Aircraft type
Lancair 235
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
N25DB
Operator
Unknown
Onboard fatalities
Unknown
Route
From Independence Municipal Airport (IDP), Independence, KSTo Independence Municipal Airport (IDP), Independence, KS
Aircraft age
About 32 years (built 1993)
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
  • Personnel issues › Task performance

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The pilot reported that he selected the landing gear down before landing, however, the landing gear did not extend. The pilot determined that it was too late to safely execute a go-around, and the airplane subsequently landed on its belly, resulting in substantial damage to the lower fuselage. The pilot reported that there were no pre-accident mechanical failures or malfunctions with the airplane that would have precluded normal operation. Postaccident examination revealed that a toggle switch that is used to energize the hydraulic system for the extension of the landing gear was inadvertently left in the OFF position by the pilot.

Probable cause

The pilot’s failure to properly configure the airplane for landing.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN25LA201
Event ID
20250609200289
Case number
CEN25LA201
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: 0726d708ede9e6d0ef6dad1195640163c75b9ef75edce5ce94da8745c9fded96; retrieved 2026-09-16T19:56:56.801Z.