FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR11CA023 · Air Tractor Inc AT-802

21 Oct 2010 · Fort Hunter Liggett, CA, United States

Air Tractor Inc AT-802 · Accident: collision with terrain/object (non-CFIT) during landing

From Fort Hunter Liggett, CA (private airstrip) to Fort Hunter Liggett, CA (private airstrip)

Report a problem

Event

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

Air Tractor Inc AT-802

Aircraft type
Air Tractor AT-802
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
N4247U
Operator
Air Tractor
Onboard fatalities
Unknown
Route
From Fort Hunter Liggett, CA (private airstrip)To Fort Hunter Liggett, CA (private airstrip)
Aircraft age
Not recorded
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
Collision with terrain/object (non-CFIT)
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 was conducting a short-field landing demonstration on a dirt airstrip. During the landing approach, the tailwheel impacted a berm of dirt located at the approach end of the airstrip. The nose pitched down and the propeller struck the runway, followed by the main landing gear. The airplane then bounced back into the air and the pilot added engine power. The airplane skidded to the left, resulting in the right main landing gear and tailwheel separating during the impact sequence. The pilot indicated that he should have landed farther down the airstrip. He reported no preimpact mechanical anomalies with the airplane that would have precluded normal operation.

Probable cause

The pilot's misjudged glide path, which resulted in a runway undershoot and collision with terrain during landing.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR11CA023
Event ID
20101022X05459
Case number
WPR11CA023
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: 02358f07c2956caa545dbd6915a3d06293825756166b3d59b83f62e82611f1dd; retrieved 2026-09-15T15:30:30.999Z.