FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

GAA19CA138 · Cessna 172RG

13 Feb 2019 · Atlanta, GA, United States

Cessna 172RG · Accident: landing gear not configured

From Fulton County Airport Brown Field (FTY) to Cobb County International Airport-McCollum Field (RYY)

Report a problem

Event

NTSB case
GAA19CA138
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

Cessna 172RG

Aircraft type
Cessna 172
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
N5223V
Operator
Unknown
Onboard fatalities
Unknown
Route
From Fulton County Airport Brown Field (FTY), Atlanta, GATo Cobb County International Airport-McCollum Field (RYY), Atlanta, GA
Aircraft age
About 39 years (built 1980)
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 › Psychological

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 of the retractable-landing gear-equipped airplane reported that, during approach, he noticed the airplane was a little high, so he reduced power to idle and heard an alert horn. He quickly scanned the engine gauges and saw that the manifold pressure gauge was "pegged at the bottom with no indication." He considered conducting a go-around but decided to land and assess the situation on the ground. The pilot landed the airplane with the landing gear retracted.

The pilot added that he did not see the landing gear position light because his iPad, which was sitting on the yoke, blocked his view. He added that, leading up to the approach and landing, the flight was fast paced, and he felt rushed, which attributed to his assumption that he was in his "typical" fixed-landing gear airplane.

The airplane sustained substantial damage to the fuselage.

The pilot reported that there were no preaccident mechanical failures or malfunctions with the airplane that would have precluded normal operation.

Probable cause

The pilot's failure to extend the landing gear before landing. Contributing to the accident were the pilot’s inability to see the landing gear position light because his iPad was blocking his view of it and his feeling of being rushed during the approach and landing.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record GAA19CA138
Event ID
20190214X71012
Case number
GAA19CA138
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: 5ffc0f3047a4da01cdc0f4512b4f1a4221754be9f3010191f01a96aedc82484d; retrieved 2026-09-16T08:35:53.494Z.