FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA20CA265 · Piper PA28R 201T

25 Jul 2020 · Fernandina Beach, FL, United States

Piper PA28R 201T · Accident: abnormal runway contact during landing

From Fernandina Beach Municipal Airport (FHB) to Fernandina Beach Municipal Airport (FHB)

Report a problem

Event

NTSB case
ERA20CA265
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 PA28R 201T

Aircraft type
Piper PA28
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
N31720
Operator
Unknown
Onboard fatalities
Unknown
Route
From Fernandina Beach Municipal Airport (FHB), Fernandina Beach, FLTo Fernandina Beach Municipal Airport (FHB), Fernandina Beach, FL
Aircraft age
About 42 years (built 1978)
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
Abnormal runway contact
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

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

NTSB narrative

The pilot reported that the airplane had just undergone an annual inspection, and this was the first flight since the work had been completed. After a normal preflight and run-up, the pilot departed, raised the landing gear, and during the initial climb, he felt an "intermittent shudder" from the engine. He reported that all of the engine parameters appeared normal, and when he reduced power in the climb the shudder stopped. The pilot subsequently decided to land immediately; he reported that on downwind in the airport traffic pattern, abeam the runway numbers, he recalled that he lowered the flaps and landing gear. He further reported that the approach was stable, and that the airplane touched down on the left main landing gear first, and as the airplane settled to the runway, the "right wing tip dropped to the runway." The airplane subsequently skidded off the runway and into terrain where the left main landing gear collapsed. The left wing and fuselage sustained substantial damage. The pilot reported that throughout the traffic pattern, he was "intently watching the engine monitor" and could not recall observing the three green landing gear down annunciator lights prior to landing, however, he recalled that the gear unsafe warning light directly in front of him was not red at any point during the flight. He reported that after the accident, when the airplane was lifted up for recovery, the right main landing gear was found retracted in its well. A witness that was located on airport property reported that he observed the airplane on short final, and the right main landing gear appeared to be retracted, but the left and nose landing gear appeared to be down. He subsequently observed the airplane touch down on the left main landing gear and roll for "quite some time" before the right wing contacted the runway. Examination of the landing gear system by a Federal Aviation Administration (FAA) Inspector following the accident found that the nose and right main landing gear functioned normally through multiple cycles. The respective green landing gear annunciator lights functioned normally, and the nose and right main landing gear fell and locked into place through the activation of the emergency gear release handle as well. The left main landing gear was disconnected from the system prior to the tests due to damage sustained in the runway excursion. The investigation was unable to duplicate any operational discrepancies with the landing gear system.

Probable cause

The failure of the right main landing gear to extend prior to landing, which could not be duplicated during postaccident tests.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA20CA265
Event ID
20200725X04434
Case number
ERA20CA265
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. 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: 6f93e58e00100ded8751b8b0f8a0091ed8ae6065bef882c2b2f3adfca64f1ed7; retrieved 2026-09-16T12:16:09.132Z.