LAX04LA269 · Newell RV-6A
Newell RV-6A · Accident: airframe, component or system failure en route
From Reid-Hillview Airport of Santa Clara County (RHV) to Hayward Executive Airport (HWD)
Narrative check · The NTSB narrative appears to contradict this record's departure or destination. Values are shown as recorded, not corrected; compare with the narrative.
Event
- NTSB case
- LAX04LA269
- 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
Newell RV-6A
- Aircraft type
- Newell RV-6
- 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
- N16TN
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route Possible conflict
- From Reid-Hillview Airport of Santa Clara County (RHV), San Luis Obispo, CATo Hayward Executive Airport (HWD), Hayward, 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
- En route · cruise
- 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
- Airframe, component or system failure
- 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 › Distance/speed, misjudged
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The airplane impacted an airport perimeter fence after the pilot landed long during a precautionary landing. The airplane was in cruise flight when the pilot noticed a loss of oil pressure and an increase in oil temperature. He assumed the engine was losing or had lost its oil and elected to make a precautionary landing at a nearby airport. The pilot reported he landed long and could not stop the airplane prior to the end of the 3,101-foot runway. Post-accident examination of the airplane revealed the oil line, from the oil cooler to the engine, failed. The pilot indicated the line was not an aircraft quality line.
Probable cause
The pilot's misjudgment of the airplane's distance/speed during a precautionary landing, which resulted in the airplane overrunning the runway. Contributing factors were failure of an oil line, and the fence.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX04LA269
- Event ID
- 20040721X01021
- Case number
- LAX04LA269
- 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: 9a6aced65524bc44c0f717c60786e2771357396516e04070f207e1b0f4468556; retrieved 2026-09-22T07:04:01.189Z.