LAX00FA206 · Beech F33A
Beech F33A · Accident: in flight collision with object during initial climb
From Columbia Airport (O22) to Oakland San Francisco Bay Airport (OAK)
Event
- NTSB case
- LAX00FA206
- 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
- 2 · all aircraft and ground
- Ground fatalities
- 0
- 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
Beech F33A
- Aircraft type
- Beechcraft 33
- 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
- N2RM
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Columbia Airport (O22), CATo Oakland San Francisco Bay Airport (OAK), Oakland, 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
- Initial climb
- 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
- In flight collision with object
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Destroyed
Cause areas
- Pilot in command › Aborted takeoff, not performed
- Pilot in command › Airspeed(vs), not attained
- Pilot in command › Compensation for wind conditions, improper
- Pilot in command › Wrong runway, selected
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
Witnesses reported seeing the airplane depart on runway 17. It became airborne about midfield, and flew nose high 10/20 feet above the 4,667-foot-long runway. Engine power was reduced, then reapplied, and the airplane crossed the runway end about 20 feet agl with the landing gear extended. The airplane collided with trees about 1,300 feet beyond the runway end. A postaccident fire erupted upon impact. One pilot witness reported the wind to be 290 degrees at 14 knots and a reported density altitude of 3,900 feet. The engine was shipped to the manufacturer for examination. According to the report, "this engine exhibits normal operational signatures throughout, except for the extensive fire and impact damages. All internal components appeared well lubricated. This engine did not exhibit any condition that would have caused an operational problem."
Probable cause
The pilot's failure to abort the downwind takeoff and his failure to attain flying speed.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX00FA206
- Event ID
- 20001212X21026
- Case number
- LAX00FA206
- 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: 4511c76935c7ca4889085036661c1670f0016060f3ac285340518aa754a2c5c8; retrieved 2026-09-20T21:12:13.854Z.