LAX87FA085 · Beech F33A
Beech F33A · Accident: loss of control in flight during initial climb
From Sacramento Executive Airport (SAC) to Visalia Municipal Airport (VIS)
Event
- NTSB case
- LAX87FA085
- 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
- 4 · 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
- N1067W
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Sacramento Executive Airport (SAC)To Visalia Municipal Airport (VIS), Visalia, 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
- Loss of control in flight
- 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 › Preflight planning/preparation, improper
- Pilot in command › Removal of control/gust lock(s), not performed
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE WINDS AT THE AIRPORT HAD BEEN REPORTED AS STRONG AND GUSTING. AFTER HIS PASSENGERS ARRIVED, THE PILOT REQUESTED AND RECEIVED TAXI INSTRUCTIONS TO THE ACTIVE RUNWAY WHICH WAS APRX 3700 FT FROM HIS PARKING SPACE. ABOUT 2-1/2 MINS AFTER RECEIVING HIS TAXI CLEARANCE, THE PILOT REQUESTED AND RECEIVED TAKEOFF INSTRUCTIONS. GROUND WITNESSES STATED THAT AFTER THE AIRCRAFT TOOK OFF, IT CLIMBED TO APRX 100 TO 200 FT, THEN ROLLED LEFT, ENTERED A STEEP DIVE & CRASHED. ABOUT 5 SEC LATER, A POST-CRASH FIRE ERUPTED. NO PREIMPACT PART FAILURE OR MALFUNCTION WAS FOUND. THE GUST LOCK PIN WAS FOUND NEAR THE CONTROL COLUMN. THE PIN WAS BENT & THE GUST LOCK PIN HOLE IN THE CONTROL COLUMN WAS ELONGATED AS THOUGH IT HAD BEEN FORCED REARWARD WITH THE PIN INSTALLED.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record LAX87FA085
- Event ID
- 20001213X30085
- Case number
- LAX87FA085
- 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: local date, investigation status. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 1987-01-14.
- API snapshot SHA-256: ef5a468faa3dbb4be8954fedd288a92473238bc386874d772411ee044b2b9803; retrieved 2026-09-21T04:15:44.461Z.