LAX05LA197 · Cessna 172L
Red Baron Aviation Cessna 172L · Accident: loss of control in flight on approach
From Santa Barbara Municipal Airport (SBA) to an unrecorded destination
Event
- NTSB case
- LAX05LA197
- 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
Cessna 172L
- Aircraft type
- Cessna 172
- 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
- N7668G
- Operator
- Red Baron Aviation
- Onboard fatalities
- Unknown
- Route
- From Santa Barbara Municipal Airport (SBA), Santa Barbara, CATo not recorded
- 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
- Approach · VFR go-around
- 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
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Stall
- 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 › Airspeed, inadequate
- Pilot in command › Stall, encountered
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 stalled and impacted the airport's ramp area during an attempted landing. While on short final approach, about 15 to 20 feet above ground level, a gust of wind lifted the left wing and shifted the airplane from the runway's centerline. The pilot manipulated the throttle control full forward in an effort to obtain the maximum power setting and execute a go-around. The airplane stalled and impacted the ramp tie-down area just north of the runway. At the time of the accident, the weather observation facility at the airport reported wind from 300 degrees at 13 knots, gusting to 21 knots. The pitch trim was found in the neutral position and the flaps were extended to 30 degrees. No preimpact mechanical malfunctions or failures were identified during an examination of the wreckage.
Probable cause
the pilot's failure to maintain adequate airspeed during a go-around in gusty wind conditions, which resulted in a stall and collision with terrain.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX05LA197
- Event ID
- 20050610X00752
- Case number
- LAX05LA197
- 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: a145546aff40732e934e1092fe1baadf1ac9f969e3c05b67b6f3d1213c8d4b8e; retrieved 2026-09-21T19:00:13.421Z.