GAA18CA302 · Taylorcraft Aviation CORP. F21 UNDESIGNAT
Taylorcraft Aviation CORP. F21 UNDESIGNAT · Accident: abnormal runway contact during landing
From Payette Municipal Airport (S75) to Payette Municipal Airport (S75)
Event
- NTSB case
- GAA18CA302
- 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
Taylorcraft Aviation CORP. F21 UNDESIGNAT
- Aircraft type
- Taylorcraft F21
- 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
- N2004U
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Payette Municipal Airport (S75), Payette, IDTo Payette Municipal Airport (S75), Payette, ID
- Aircraft age
- About 38 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
- 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 oper/perf/capability
- Environmental issues › Conditions/weather/phenomena
- 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
According to the student pilot in the tailwheel-equipped airplane, he had completed a cross-country flight and aborted the first landing due to crosswind gusts from the left. He also aborted the second landing, but on his third approach about 60 knots, he committed to the landing. Just before touching down, the airplane encountered a left crosswind gust and then touched down oriented 10° left of the runway heading and bounced. The airplane veered right and exited the right side of the runway. He added full power and aborted the landing, but the airspeed was too slow. The airplane remained airborne for 150 ft, landed in a dirt field, and nosed over.
The airplane sustained substantial damage to the left wing and windscreen.
The student reported that, at the time of the accident, "winds were out of the NW at approximately 11 mph (as indicated by my Garmin Pilot app) with a 6 mph crosswind from the West and gusting." The airplane landed on runway 31.
The nearest METAR, which was 6 miles southwest of the accident site, reported that, about the time of the accident, the wind was from 300° at 10 knots.
The student reported that there were no mechanical malfunctions or failures with the airplane that would have precluded normal operation.
Probable cause
The student pilot’s failure to maintain directional control during landing with a crosswind and his subsequent failure to maintain airspeed during an aborted landing, which resulted in a collision with terrain and nose-over.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record GAA18CA302
- Event ID
- 20180529X42913
- Case number
- GAA18CA302
- 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: 085da083fb8db9563f1322f2cd08191fd4f289b3673c80c8b75aece8e2be8d76; retrieved 2026-09-16T07:18:21.127Z.