GAA17CA126 · Piper PA32R 300
Piper PA32R 300 · Accident: landing gear not configured
From Sun Valley Airport (A20) to Redlands Municipal Airport (REI)
Event
- NTSB case
- GAA17CA126
- 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
Piper PA32R 300
- Aircraft type
- Piper PA32
- 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
- N6885F
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Sun Valley Airport (A20), Bullhead City, AZTo Redlands Municipal Airport (REI), Redlands, CA
- Aircraft age
- About 41 years (built 1976)
- 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
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The pilot reported that, during the initial climb, he retracted the landing gear normally and then "a few minutes later the radios went blank." He believed he had a radio problem, so he decided to return to the airport. During the return, the pilot moved the landing gear selector to the down position, but the three gear down indicator lights did not illuminate. Subsequently, the pilot circled a few miles east of the airport to troubleshoot the issue.
The pilot reported that, during the circling, he "cycled the master switch and the radio master a couple times with no results." The pilot added that the airplane was equipped with an "automatic gear extension system," so he verified that the override switch was not engaged, fully extended the flaps, and slowed the airplane to 85 knots. Subsequently, the pilot believed the landing gear was down, so he returned to the airport for landing. During touchdown, the left main landing gear and nose gear collapsed (or were not extended), and the airplane veered off the runway into dirt, which resulted in substantial damage to the left wing. During a postaccident interview, the pilot reported that he believed he had "a total electrical failure."
According to a witness who owns a house on the airport property, he observed the airplane depart and about 5 minutes later, saw that the airplane had returned for landing. The witness reported that the airplane's landing gear were retracted until the point at which the pilot began the landing flare over the runway. When the airplane was about 5 ft above the runway, each landing gear began to extend, but the airplane touched down before the nose gear and left main landing gear could extend fully.
According to a Federal Aviation Administration (FAA) aviation safety inspector (ASI) who arrived at the accident site about 2 to 3 hours after the event, when he "switched the master switch on," he observed electrical equipment turn on and heard the landing gear extension motor running. During a subsequent postaccident examination, the FAA ASI reported that he found no abnormalities with the electrical system. He also extended the landing gear to the down-and-locked position with the electric/hydraulic system and observed three green indicator lights illuminate.
According to the Pilot's Operating Handbook (POH) for the accident airplane, a "pressure sensing device" in the landing gear system will lower the gear "regardless of the gear selection position," pending that the override switch is not engaged. The POH further stated, in part, "The gear is designed to extend at airspeeds below approximately103 KIAS [knots indicated airspeed] with power off even if the selector is in the up position. The extension speeds will vary from approximately 81 KTS [knots] to approximately 103 KIAS depending on power settings and altitude."
It is likely that the pilot failed to extend the landing gear for landing and that, as the airspeed slowed during the landing flare, the pressure sensing device automatically deployed the landing gear. However, due to the insufficient altitude and time, the landing gear were unable to fully extend and lock.
Probable cause
The pilot's failure to extend the landing gear for landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record GAA17CA126
- Event ID
- 20170130X42804
- Case number
- GAA17CA126
- 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: 74a068058db216972f751e1a5fc8127ee02e408c3687e17fb806d50465a54d78; retrieved 2026-09-16T04:58:41.270Z.