GAA19CA375 · Cessna 172 S
Westwind School of Aeronautics Phoenix Cessna 172 S · Accident: loss of control in flight during landing
From Phoenix Deer Valley Airport (DVT) to Phoenix Deer Valley Airport (DVT)
Event
- NTSB case
- GAA19CA375
- 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 172 S
- 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
- N606JA
- Onboard fatalities
- Unknown
- Route
- From Phoenix Deer Valley Airport (DVT), Phoenix, AZTo Phoenix Deer Valley Airport (DVT), Phoenix, AZ
- Aircraft age
- About 18 years (built 2001)
- 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 · flare/touchdown
- 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
- Loss of control in flight
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Pole
- 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 oper/perf/capability
- Personnel issues › Action/decision
- Personnel issues › Task performance
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The flight instructor reported that, while the student pilot was making a soft-field landing, the airplane's nose was high, and the student chose to go around before touchdown. The airplane did not climb and drifted left. The instructor assumed control of the airplane and attempted to correct by pitching the nose down, adding full power, and decreasing flaps to 20°. However, the airplane did not climb or accelerate and continued to drift left. Subsequently, the airplane touched down and bounced on the gravel infield, entered the ramp area, and impacted a light pole.
The airplane sustained substantial damage to the both wings.
The instructor reported that there were no preaccident mechanical failures or malfunctions with the airplane that would have precluded normal operation.
The airport's automated weather observation station reported that, about 20 minutes after the accident, the wind was from 180° at 4 knots. The student was landing the airplane on runway 7L.
Probable cause
The student pilot's improper landing flare and failure to maintain the runway heading, which resulted in the loss of airplane control, and the flight instructor's delayed remedial action during a go-around with a crosswind, which resulted in a bounced landing and subsequent impact with a pole.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record GAA19CA375
- Event ID
- 20190628X64031
- Case number
- GAA19CA375
- 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: 5082ae5a18957ba5a6ae2b9ca33393df866a6f3720ded0fb79d68b1741f49e0a; retrieved 2026-09-16T09:20:01.282Z.