Gear Won't Come Down
Landing gear extension failure on approach to Brooksville — a complex-aircraft emergency with limited options and a decision clock measured in minutes
The scenario
Departing Brooksville–Tampa Bay Regional Airport (KBKV), Brooksville, FL — Runway 09, a 7,001-ft concrete runway. Elevation 76 ft MSL. You are a commercial pilot with 800 hours total time, 200 hours in the Piper Arrow (PA-28R-200). This is a local proficiency flight — a 1.5-hour round trip to a nearby field and back.
It is a clear, calm Florida afternoon: OAT 24°C, dew point 18°C, altimeter 30.01, winds calm. Visibility 10 SM. VFR all the way. You departed KBKV at 1430 local, climbed to 3,500 ft MSL, and spent 45 minutes practicing slow flight and steep turns in the practice area east of the field. You are now on descent back to KBKV, 8 nm out, 2,000 ft MSL, heading 270° for a left downwind to Runway 09.
Aircraft: Piper Arrow PA-28R-200, solo, 1,200 lbs fuel (full tanks), within CG and weight limits. The airplane was last serviced 10 days ago — routine 100-hour inspection, no write-ups. The landing gear hydraulic system, emergency extension system, and gear indicators were all tested and signed off. Nothing was written up.
Pilot: you — a commercial pilot, current, 800 hours total, 200 hours in type. You are familiar with KBKV; you have landed here 12 times. You are not fatigued, not distracted, and the flight has been routine.
KBKV is Class D airspace (ceiling 1,500 ft MSL), towered part-time 0700–2200 local. The tower is open and active. Runway 09's climb-out environment is open developed (parks/large lots), pasture/hay, and medium development — good off-field options if needed. Runway 27's environment is low-density development, pasture/hay, and grassland — also good. This is not a water-surrounded field; forced landings off either runway end have reasonable off-field options.
- {'label': 'Field', 'value': 'KBKV · Brooksville–Tampa Bay'}
- {'label': 'Runways', 'value': '3/21 · 9/27'}
- {'label': 'Elevation', 'value': '76 ft'}
- {'label': 'Aircraft', 'value': 'PA-28R'}
- {'label': 'Dominant phase', 'value': 'Landing / Cruise'}
The decision
Before we get into the decision tree — what do you already know about landing gear emergencies in the Piper Arrow? (Pick all that apply; this records your baseline.)
What the record shows
What the NTSB files show
NTSB CEN23LA417 (2023): A Piper PA-28RT-201 experienced partial retraction of the right main and nose landing gear during landing rollout at an unspecified airport. The cause of the gear retraction could not be determined despite extensive testing. The probable cause was listed as 'partial retraction of the right main and nose landing gear during landing rollout for undetermined reasons.' This scenario shows that gear malfunctions can occur even after normal extension and landing — a post-landing failure, not a pre-landing one.
NTSB WPR22LA040 (2021): A Piper PA-28R-200 on a personal flight had a right main landing gear that would not extend during approach. The aircraft landed on the left main and nose landing gear only. The accident investigation found that the installation of an improper right main landing gear door rod-end bolt prevented the landing gear from extending. This is a post-maintenance failure — the improper bolt was installed during a recent service. The pilot did not use emergency extension procedures and landed on two gear instead of three. The aircraft sustained damage but remained on the runway.
NTSB ERA15LA289 (2015): A Piper PA-28R-180 on an instructional flight at Fort Lauderdale Executive Airport experienced an unsafe nose landing gear indication and performed emergency extension procedures. The investigation found undetected fatigue cracks in the nose landing gear strut mount assembly that prevented proper gear alignment after extension. The pilots lost directional control after touchdown and the aircraft exited the runway. The probable cause was 'undetected fatigue cracks in the engine and nose landing gear strut mount assembly, which prevented the proper alignment of the NLG after it was extended and the pilots from being able to maintain directional control after touchdown.'
NTSB CEN11LA418 (2011): A Piper PA-28R-201 made a wheels-up landing after the landing gear power pack motor failed. The pilot did not use the emergency landing gear extension system. The probable cause was 'the pilot did not use the emergency landing gear extension system, which resulted in a wheels-up landing. Contributing to the accident was the inoperative landing gear power pack motor.' This is the critical lesson: when the hydraulic system fails, the emergency extension system is the backup. Failure to use it results in a wheels-up landing.
The real accidents cited above occurred at other airports and in other aircraft — NOT at Brooksville–Tampa Bay Regional Airport (KBKV). KBKV has its own accident history (dominant patterns: hard landing 26.9%, forced landing 11.5%, runway excursion 11.5%), but these specific landing gear events happened elsewhere. The scenario is localized to KBKV to make the off-field environment real and the decision-making consequential for you as a student here.
The consistent thread across all these events: landing gear malfunctions in the Piper Arrow are often post-maintenance failures (improper bolt installation, fatigue cracks) or hydraulic system failures. The fix is always the same: declare emergency early, execute emergency extension procedures per the POH, confirm all three green lights, and land normally. Failure to use the emergency extension system (CEN11LA418) or failure to declare emergency and troubleshoot (WPR22LA040) results in a wheels-up landing or a landing on fewer than three gear. The decision window is measured in minutes, not hours. At KBKV, the off-field environment off Runway 09 is open developed (parks/large lots), pasture/hay, and medium development — good forced-landing options if the emergency extension fails. But the goal is always to get the gear down and land normally.
Key lesson — In the Piper Arrow, a landing gear malfunction is a complex-aircraft emergency that requires immediate declaration, systematic troubleshooting, and execution of emergency extension procedures. The red light (unsafe gear indication) is not a faulty indicator — it is a real warning. Do not assume the gear is down; verify it with the emergency extension system. At KBKV, the off-field environment is good (open developed, pasture, medium development), but the goal is always to get the gear confirmed down and land on the runway. The decision window is short — declare emergency early, execute emergency extension at safe altitude, confirm all three green lights, and land normally. Delay or complacency leads to a wheels-up landing.
Debrief — teaching points
A red light (unsafe gear indication) is a real warning — do not assume it is a faulty indicator.
In the Piper Arrow, the landing gear warning light (red) indicates at least one gear is not fully down and locked. This is not a faulty indicator that you can ignore. The light is part of a safety system designed to prevent wheels-up landings. If the red light is on, the gear is not confirmed down. The correct response is to declare emergency, execute emergency extension procedures per the POH, and confirm all three green lights before landing. Assuming the light is faulty and landing anyway is the path to a wheels-up landing (NTSB CEN11LA418).
Declare emergency early — do not wait until you are on final approach.
When the landing gear will not extend, declare emergency with ATC immediately. This gives you tower support, a clear runway, and time to execute emergency procedures without time pressure. Declaring at 6 nm from the field gives you 5–10 minutes to troubleshoot and execute. Declaring at 1 nm gives you 2–3 minutes. Declaring on final approach at 500 ft AGL leaves no margin for error. Early declaration is not a sign of weakness; it is airmanship.
Execute emergency extension procedures per the POH — this is the backup system when the hydraulic system fails.
The Piper Arrow has an emergency landing gear extension system (manual crank or backup hydraulic, depending on the variant). This system is designed to lower the gear when the main hydraulic system fails. The POH procedure must be followed exactly: reduce airspeed to below Vle (129 KIAS), engage the emergency system, and wait for the green lights. The procedure takes 30–45 seconds. Do not skip this step or assume the gear is down without it. Failure to use the emergency system results in a wheels-up landing (NTSB CEN11LA418).
Vle (129 KIAS) is the maximum speed with landing gear extended — do not exceed it during emergency extension.
The maximum speed with landing gear extended is 129 KIAS (Vle). Exceeding this speed can damage the gear or the gear doors. During emergency extension procedures, reduce airspeed to below 129 KIAS and maintain that speed until the green lights illuminate. This is not optional; it is a structural limit.
At KBKV, the off-field environment off Runway 09 is good — but the goal is always to get the gear down and land on the runway.
The off-field environment off Runway 09's climb-out (heading 090°) is open developed (parks/large lots), pasture/hay, and medium development — good forced-landing options if the emergency extension fails. However, the goal is always to get the gear confirmed down and land on the runway. A forced landing off-field is a last resort, not a primary option. Execute emergency extension procedures, confirm the gear is down, and land normally.
Post-maintenance failures are common in landing gear systems — inspect the gear system carefully after any maintenance.
NTSB WPR22LA040 shows a landing gear malfunction caused by an improper rod-end bolt installed during maintenance. Post-maintenance failures are a known risk in complex systems. After any maintenance on the landing gear, hydraulic system, or gear doors, perform a thorough preflight inspection and test the gear extension/retraction cycle on the ground before flight. Do not assume the maintenance was done correctly.
Built from the real accident record
Scenario built from NTSB CEN23LA417 (2023 PA-28RT partial gear retraction during landing rollout), WPR22LA040 (2021 PA-28R-200 right main gear extension failure due to improper door rod-end bolt), ERA15LA289 (2015 PA-28R-180 unsafe nose gear indication and directional control loss), and CEN11LA418 (2011 PA-28R-201 wheels-up landing after failure to use emergency extension). Localized to Brooksville–Tampa Bay Regional Airport (KBKV).
NTSB reports: CEN23LA417 · WPR22LA040 · ERA15LA289 · CEN11LA418
ACS tasks: PA.I.F — Weather Information · PA.I.G — Cross-Country Flight Planning · PA.IX.C — Emergency Approach and Landing · PA.I.H — Human Factors · PA.II.A — Preflight Inspection · PA.II.B — Engine Starting / Systems Preflight
Relevant FARs: §91.3 · §91.13 · §91.185
Step through the full decision tree, make the calls, and see where each choice leads — then debrief it with your CFI.
Open the interactive scenario →All sample scenarios · More Piper Arrow scenarios · More scenarios at KBKV