FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

LAX04CA185 · Aeronca 65-TAC

12 Apr 2004 · Grass Valley, CA, United States

Aeronca 65-TAC · Accident: loss of control on ground/water during landing

From Watts Woodland Airport (O41) to Alta Sierra Airport (09CL)

Report a problem

Event

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

Aeronca 65-TAC

Aircraft type
Aeronca 65
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
N39515
Operator
Unknown
Onboard fatalities
Unknown
Route
From Watts Woodland Airport (O41), Woodland, CATo Alta Sierra Airport (09CL), Grass Valley, CA
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 · landing roll
First occurrenceThe 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/water
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

  • Pilot in command › Compensation for wind conditions, inadequate
  • Pilot in command › Directional control, not maintained

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 experienced a loss of directional control, veered off the runway, and collided with trees while on the landing roll. The pilot stated that the runway he was attempting to land on is solely used for landing at the airport, due to an excessive gradient. During the approach, the pilot noted tailwind conditions and opted to perform a wheel landing. While on the landing roll, the airplane encountered a gust of wind from the right, resulting in the tail being pushed to the left. The airplane veered to the right and began a 45-degree arc off the right side of the runway. The pilot applied full left rudder pressure and left brake to counteract the veer. The airplane departed the right side of the runway and collided with trees. The pilot stated that on the right side of the runway are two groups of dense trees. In between the tree groups, about halfway down the runway, air funnels through creating wind gusts. He thought this was why he encountered sudden crosswind gusts. The pilot reported no preimpact mechanical malfunctions or failures with the airplane. The pilot reported that the winds were from 190 degrees at 5 knots.

Probable cause

the pilot's inadequate compensation for wind conditions and failure to maintain directional control of the airplane. Factors in the accident were wind gusts and tailwind/crosswind conditions.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record LAX04CA185
Event ID
20040430X00541
Case number
LAX04CA185
Dataset
historical-pre2008
Source SHA-256
89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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: b0a92ece21e36c1a131e2d2f81f6cef89e3d5494b90ca11f5282127782de3211; retrieved 2026-09-22T07:44:27.673Z.