Gear Down and Locked — Or Is It?
A landing-gear extension malfunction on approach to KPIE forces an abnormal-gear decision in a complex aircraft
The scenario
Departing St. Petersburg Clearwater International Airport (KPIE), Pinellas Park, FL — Runway 18, a 9,730 ft concrete runway. Elevation 11 ft MSL. You are on a local training flight in a Piper Arrow PA-28R, solo, within weight and balance limits, full fuel, 1.8 hours endurance. The airplane was released from maintenance this morning after a routine 100-hour inspection; the landing gear system was inspected and serviced as part of the work.
It is a clear, calm afternoon: OAT 26°C, winds 090° at 4 kt, visibility 10 SM. Class D airspace, tower active (0600–2300 local). You are at 2,500 ft MSL, 8 nm northeast of KPIE, on a descent to enter the pattern for Runway 18. The approach is routine. You have 200 hours total, 40 hours in the Arrow, and are working toward your commercial certificate.
At 1,500 ft MSL on the downwind leg, you lower the landing gear. The gear-down indicator light illuminates — three green lights, nose and both mains. The gear selector is DOWN. Everything appears normal. You continue the descent to the base leg.
On short final, 500 ft AGL, you perform the landing checklist: fuel selector LEFT (you are on the left tank), mixture rich, prop full forward (constant-speed prop at high RPM for landing), flaps 20°, airspeed 75 KIAS (Vref). The three green lights are still lit. You are stable on the glide slope, 3° descent, 79 KIAS (best glide speed for a go-around if needed).
At 200 ft AGL, you hear a loud CLUNK from the landing gear area — a distinct mechanical sound, not normal. The three green lights remain lit. But something is wrong. You have 30 seconds to the runway.
- {'label': 'Field', 'value': 'KPIE · St. Petersburg Clearwater'}
- {'label': 'Runways', 'value': '4/22 · 18/36'}
- {'label': 'Elevation', 'value': '11 ft'}
- {'label': 'Aircraft', 'value': 'PA-28R'}
- {'label': 'Dominant phase', 'value': 'Takeoff / Landing'}
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. The right wing scraped the runway, and the aircraft exited the runway. The cause of the partial retraction could not be determined despite extensive testing. The three green lights were lit throughout the landing and rollout — but the gear partially retracted anyway, suggesting a mechanical failure in the gear-locking mechanism or a post-maintenance installation error.
NTSB WPR22LA040 (2021): A Piper PA-28R-200 had a right main landing gear that would not extend during approach. The aircraft landed on the left main and nose gear. The investigation revealed an improper right main landing gear door rod-end bolt installed during maintenance — the bolt prevented the gear from extending fully. The three green lights may have illuminated (indicating the gear was 'down'), but the right main was not actually locked or fully extended.
NTSB ERA15LA289 (2015): A Piper PA-28R-180 experienced an unsafe nose gear indication and performed emergency extension procedures. The investigation revealed undetected fatigue cracks in the nose landing gear strut mount assembly. After extension, the nose gear was not properly aligned, causing directional control loss during landing rollout and a runway excursion. The unsafe indication (red or amber light) was the correct warning — the gear was not fully locked.
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 three green lights did not illuminate (indicating an unsafe condition), but the pilot did not recognize the unsafe indication or did not know how to use the emergency extension system. The result was a wheels-up landing.
The common thread across all these accidents: landing gear malfunctions in the Piper Arrow are often subtle. A mechanical clunk, an unusual sound, or a partial retraction can occur even when the three green lights are lit. Post-maintenance failures (improper bolt installation, fatigue cracks) are a significant cause. The emergency landing gear extension system is the backup — and it must be used if there is any doubt about the normal system.
The real accidents cited above occurred at other airports and in other aircraft — NOT at KPIE. However, KPIE's own accident corpus shows GEAR_UP_LANDING as 9.1% of accidents — a significant pattern. The scenario is localized to KPIE to make the decision real for you as a student here.
The lesson: three green lights are the primary indication, but they are not infallible. A mechanical clunk or unusual sound is a warning sign. If you have any doubt, cycle the gear to confirm it operates, request a visual inspection, or use the emergency extension system. Do not land on the belly unless you have an unsafe indication (red or amber light) and the gear will not extend by any means.
Key lesson — In the Piper Arrow, landing gear malfunctions can be subtle. A mechanical clunk with three green lights is a gray area — the lights say 'down and locked,' but the clunk says 'something is wrong.' The correct response is to troubleshoot: cycle the gear, request a visual inspection, or use the emergency extension system. Do not assume the lights are wrong and land on the belly unless you have an unsafe indication (red or amber light). A wheels-up landing or belly landing is survivable, but it is a last resort — not the first response to an unusual sound.
Debrief — teaching points
Three green lights are the primary landing gear indication in the Piper Arrow.
The three green lights (nose and both mains) indicate that the gear is down and locked. This is the only reliable electrical indication in the Arrow. A red light (unsafe) or amber light (transition) means the gear is not down and locked. However, three green lights are not infallible — they indicate the gear position as sensed by the limit switches, not the mechanical lock status. A post-maintenance installation error (improper bolt, fatigue crack) can cause the lights to be wrong.
A mechanical clunk or unusual sound from the gear area is a warning sign — do not ignore it.
NTSB CEN23LA417 and WPR22LA040 both involved mechanical failures that occurred despite three green lights. A clunk at 200 ft AGL is a red flag. The correct response is to troubleshoot: cycle the gear to confirm it operates smoothly, request a visual inspection from the tower, or use the emergency extension system. Do not assume the lights are correct and land immediately.
Gear cycling at altitude is a valid troubleshooting step.
If you hear an unusual sound or have any doubt about the gear, cycle it at a safe altitude (1,000 ft AGL or higher). Retract the gear fully, wait 10 seconds, then extend it again. If the mechanism operates smoothly and the three green lights illuminate after extension, you have confirmed the gear is functioning. This is a low-risk troubleshooting step that takes 30 seconds and gives you confidence.
The emergency landing gear extension system is a mechanical backup — know how to use it.
The Piper Arrow has an emergency landing gear extension system (manual crank or CO2 bottle, depending on the model). If the normal system fails or you have any doubt about the normal system, use the emergency extension. NTSB CEN11LA418 involved a pilot who did not use the emergency system and landed wheels-up unnecessarily. Know where the emergency extension control is located and how to operate it before you fly.
Do not land on the belly unless you have an unsafe indication and the gear will not extend by any means.
A wheels-up landing or belly landing is survivable, but it is a last resort. The correct sequence is: (1) three green lights = land normally; (2) unsafe indication (red or amber light) = troubleshoot and use emergency extension; (3) gear will not extend by any means = declare emergency and plan belly landing. Do not skip to step 3 because you heard an unusual sound. NTSB CEN11LA418 and the scenario's outcome n12 show the cost of landing on the belly unnecessarily.
Post-maintenance failures are a significant cause of landing gear malfunctions.
NTSB WPR22LA040 involved an improper bolt installation during maintenance. NTSB ERA15LA289 involved undetected fatigue cracks. After any maintenance on the landing gear system, perform a thorough preflight check: cycle the gear on the ground (if possible), confirm the three green lights illuminate, and listen for unusual sounds. If the airplane was released from maintenance this morning (as in the scenario), be extra vigilant for post-maintenance failures.
At KPIE, landing gear malfunctions are a significant accident pattern — 9.1% of accidents.
KPIE's own accident corpus shows GEAR_UP_LANDING as 9.1% of accidents — a significant pattern. This is not a rare event. Gear-up landings and gear malfunctions are a known risk at this field. Treat every landing gear indication seriously. Do not assume the lights are correct. Troubleshoot, confirm, and land with confidence.
Built from the real accident record
Scenario built from NTSB CEN23LA417 (2023 PA-28RT partial gear retraction during landing rollout), WPR22LA040 (2021 PA-28R 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 KPIE.
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.D — Landing Gear Systems · PA.II.E — Flight Controls
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 KPIE