FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

GAA16CA411 · Beech F33 A

1 Aug 2016 · Blythe, CA, United States

Beech F33 A · Accident: loss of control in flight during initial climb

From Blythe Airport (BLH) to Henderson Executive Airport (HND)

Report a problem

Event

NTSB case
GAA16CA411
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

Beech F33 A

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
N6728X
Operator
Unknown
Onboard fatalities
Unknown
Route
From Blythe Airport (BLH), Blythe, CATo Henderson Executive Airport (HND), Las Vegas, NV
Aircraft age
About 33 years (built 1983)
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
Defining eventThe 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
Substantial

Cause areas

  • Aircraft › Aircraft oper/perf/capability
  • Personnel issues › Task performance

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

The pilot was conducting a night, visual meteorological conditions flight from a rural desert airport, and reported that prior to the flight, she did a weight and balance, checked the temperature, and did performance calculations.

The pilot reported that after rotation, the airplane was not producing "sufficient power and not climbing as anticipated" and the stall warning horn was audible. She lowered the airplane's nose, and the stall warning horn silenced. The pilot further reported that she heard "scraping" [ground impact] against the airplane, but she could not see the terrain due to the night conditions. Subsequently, the airplane impacted the ground off of the airport, which resulted in substantial damage to the fuselage.

In a follow up email conversation with the pilot's attorney, the attorney said that the pilot reported that the engine was producing power at the time that the aerodynamic stall warning horn was audible and just before impact, but noted that the power was not sufficient.

A photograph of the accident airplane provided by the FAA inspector that responded to the accident, showed all three blades exhibited tip curl, torsional twisting and S-bending, consistent with the engine producing power at the time of impact.

The airplane performance and weight and balance calculations that the pilot performed prior to the accident flight were requested by the National Transportation Safety Board investigator-in-charge (IIC), but were not provided.

The pilot stated she was unaware of any preaccident mechanical malfunctions or failures with the airplane that would have precluded normal operation.

It is likely that the pilot exceeded the critical angle of attack during takeoff at night resulting in an aerodynamic stall.

The Federal Aviation Administration has published the Airplane Flying Handbook FAA-H-8083-3A (2004). This handbook discusses aerodynamic stalls and states in part:

The key to stall awareness is the pilot's ability to visualize the wing's angle of attack in any particular circumstance, and thereby be able to estimate his/her margin of safety above stall. This is a learned skill that must be acquired early in flight training and carried through the pilot's entire flying career. The pilot must understand and appreciate factors such as airspeed, pitch attitude, load factor, relative wind, power setting, and aircraft configuration in order to develop a reasonably accurate mental picture of the wing's angle of attack at any particular time. It is essential to flight safety that a pilot takes into consideration this visualization of the wing's angle of attack prior to entering any flight maneuver.

Stall accidents usually result from an inadvertent stall at a low altitude in which a recovery was not accomplished prior to contact with the surface.

Probable cause

The pilot's failure to attain adequate airspeed to climb and her exceedance of the airplane's critical angle-of-attack during takeoff initial climb at night, which resulted in an aerodynamic stall at low altitude.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record GAA16CA411
Event ID
20160803X03110
Case number
GAA16CA411
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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: 6f9fa700e14a89f757c0226c65b67ddc543356e959d04b4cf7a2d6823eeb85bc; retrieved 2026-09-16T03:45:20.929Z.