LAX07CA018 · Codding/Fluno Sportsman GS-2
Codding/Fluno Sportsman GS-2 · Accident: on ground/water encounter with weather during landing
From Charles M. Schulz Sonoma County Airport (STS) to Hopland, CA
Event
- NTSB case
- LAX07CA018
- 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
Codding/Fluno Sportsman GS-2
- Aircraft type
- Codding/fluno SPORTSMAN GS-2
- 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
- N429AD
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Charles M. Schulz Sonoma County Airport (STS), Santa Rosa, CATo Hopland, 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
- On ground/water encounter with weather
- 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 › Brakes(normal), excessive
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The experimental amateur-built airplane nosed over after the pilot applied firm braking during the landing roll. The pilot landed the tailwheel equipped airplane on his grass airstrip after assessing the wind direction with the aide of a windsock. During the landing roll the pilot realized that the remaining runway was decreasing and applied firm braking. The airplane nosed over and came to rest inverted. Upon exiting the airplane the pilot noticed the wind was blowing from a direction opposite than the windsock indicated. He examined the windsock and found that it was caught in a guide wire and was indicating opposite the actual wind direction.
Probable cause
the pilot's excessive braking during landing roll, which resulted in the airplane nosing over. A contributing factor was the erroneous windsock indication, which prompted the pilot to land with a tailwind, and inadvertently increase his landing roll.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX07CA018
- Event ID
- 20061129X01721
- Case number
- LAX07CA018
- 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. 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: ca1f50a6629f86c7e2602a79596d84f604d241ec6b6c4c8e83bd640cfbc59979; retrieved 2026-09-22T04:18:16.403Z.