FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN25LA120 · Piper PA-28R-200

12 Mar 2025 · Lincoln, NE, United States

Revv Aviation Piper PA-28R-200 · Accident: landing gear not configured

From Council Bluffs Municipal Airport (CBF) to Council Bluffs Municipal Airport (CBF)

Report a problem

Event

NTSB case
CEN25LA120
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
Event fatalities
Unknown
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

Piper PA-28R-200

Aircraft type
Piper PA-28
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
N93TJ
Onboard fatalities
Unknown
Route
From Council Bluffs Municipal Airport (CBF), Council Bluffs, IATo Council Bluffs Municipal Airport (CBF), Council Bluffs, IA
Aircraft age
About 56 years (built 1969)
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
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 from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

The flight instructor and the pilot receiving instruction were conducting an instructional flight and entered the airport traffic pattern with two airplanes ahead of them. Shortly afterward, the instructor directed the pilot receiving instruction to lower the landing gear and partially extend the wing flaps. However, the instructor noted that the number of radio transmissions between the tower controller and the airplanes in the traffic pattern caused some distractions. He stated that a GUMPS check was completed turning onto final approach. However, during the landing flare when the engine power was reduced, he heard a horn followed shortly by a grinding noise from the propeller contacting the runway pavement. The pilot receiving instruction reported that upon entering the airport traffic pattern, he partially extended the wing flaps on downwind but did not extend the landing gear at that time. Due to the multiple radio transmissions and sequencing with other airplanes in the traffic pattern, he did not recall hearing the landing gear call from the flight instructor nor did he have time to look at the checklist. He noted that it was late by the time he noticed the landing gear was not extended. After touching down, the airplane departed the runway pavement and came to rest upright in the adjacent grass area. The left outboard wing struck a runway distance remaining sign which resulted in substantial damage to the airframe. A postaccident examination conducted by a maintenance technician responding to the accident site determined that the right main landing gear appeared down and locked; however, the left main and nose landing gears were not. The cockpit landing gear selector was in the up position. When the airplane master switch was turned on, the landing gear warning horn sounded. Upon lifting the airplane, the left main and nose landing gears extended into the over center and locked positions. When the landing gear selector was moved to the down position, the hydraulic pump started running and the gear indicator lights showed green. The flight instructor stated that, in a “moment of complacency,” he failed to verify the landing gear position. The landing gear horn did not activate until the engine power was reduced to idle upon entering the landing flare due to the need to maintain engine power during the approach. Similarly, the landing gear autoextension system did not activate until the engine power was reduced to idle during the landing flare.

Probable cause

A failure of the flight crew to ensure that the landing gear was properly extended before landing.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN25LA120
Event ID
20250313199850
Case number
CEN25LA120
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, 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: b1bcc61437de32b885d3adf15a6bb349896ea544f90714fd9213b11307e3a777; retrieved 2026-09-16T19:44:09.705Z.