FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

GAA17CA123 · Piper PA 28R 200

24 Jan 2017 · Wichita, KS, United States

Piper PA 28R 200 · Accident: loss of control on ground during landing

From Wichita Dwight D. Eisenhower National Airport (ICT) to Wichita Dwight D. Eisenhower National Airport (ICT)

Report a problem

Event

NTSB case
GAA17CA123
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 PA 28R 200

Aircraft type
Piper PA-28
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
N4792T
Operator
Unknown
Onboard fatalities
Unknown
Route
From Wichita Dwight D. Eisenhower National Airport (ICT), Wichita, KSTo Wichita Dwight D. Eisenhower National Airport (ICT), Wichita, KS
Aircraft age
About 45 years (built 1972)
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
Loss of control on ground
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 › Task performance

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

NTSB narrative

The pilot reported that, during the landing roll in gusting crosswind conditions, the airplane veered off the runway to the left into the grass. During the runway excursion, the right wing impacted an airport sign, which resulted in substantial damage. After the airplane had stopped, the pilot taxied to the ramp without further incident.

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

A review of recorded data from the automated weather observation station located on the airport revealed that, about 2 minutes before the accident, the wind was from 310° at 22 knots, gusting to 27 knots. The airplane landed on runway 1R.

According to the Pilot's Operating Handbook for the accident airplane, the maximum demonstrated crosswind component for the airplane is 20 miles per hour/17.3 knots.

Probable cause

The pilot's failure to maintain directional control while landing in gusting crosswind conditions.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record GAA17CA123
Event ID
20170126X12752
Case number
GAA17CA123
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: 8b6adc84336a107f2e61d568b4b910745dfad1f2a719ccb41bb6a8bd78ad20be; retrieved 2026-09-16T04:58:13.563Z.