FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA12FA326 · Gutierrez Pablino HUMMEL BIRD

9 May 2012 · DeFuniak Springs, FL, United States

Gutierrez Pablino HUMMEL BIRD · Accident: aerodynamic stall/spin during initial climb

From Defuniak Springs Airport (54J) to Defuniak Springs Airport (54J)

Report a problem

Event

NTSB case
ERA12FA326
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
1 · 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

Gutierrez Pablino HUMMEL BIRD

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
N9001N
Operator
Unknown
Onboard fatalities
Unknown
Route
From Defuniak Springs Airport (54J), DeFuniak Springs, FLTo Defuniak Springs Airport (54J), DeFuniak Springs, FL
Aircraft age
About 2 years (built 2010)
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
Aerodynamic stall/spin
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 › Experience/knowledge
  • Personnel issues › Task performance

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

Witnesses reported observing the airplane porpoising along its longitudinal axis during its climb after takeoff. About 300 feet above ground level, the airplane pitched up to a nose-high attitude and rolled to the right; it subsequently impacted the ground in a right-wing-low, nose-down attitude. Postaccident examination did not reveal any preimpact mechanical malfunctions or abnormalities that would have precluded normal operation. However, the weight of the airplane (not including fuel) plus the weight of the pilot exceeded the airplane's maximum gross takeoff weight and the center of gravity (CG) was aft of the most rearward limit. Although any fuel would have moved the CG forward of the most rearward limit, it also would have increased the airplane's takeoff weight. The pilot reported to his aviation medical examiner (AME) that the airplane was having "great" difficulty with longitudinal stability. He also noted that his weight gain caused the airplane to be "over gross," most likely causing the control problems. The AME advised the pilot to stop flying the airplane.

Because the airplane was at or aft of the rear CG limit, it would have been very sensitive in pitch control and may even have been at or near a dynamically unstable flight regime in terms of pitch handling. Accordingly, the airplane would have required more nose-down trim adjustment. Additionally, because stall speeds increase as gross weight increases, the airplane would have stalled at a higher airspeed. Therefore, it is likely that, during the climb, the airplane stalled at a higher airspeed than the pilot would have expected due to its exceedence of the maximum gross weight and that it subsequently entered a spin.

A review of the pilot's logbook indicated that he had accumulated only 4.4 flight hours in the 2 years preceding the accident flight with only 0.3 hour in the accident airplane. It is likely that the pilot's lack of experience in the airplane make and model contributed to his decision to take off with the airplane in an overweight condition and his inability to understand the seriousness of the situation. Although the postmortem toxicology testing was positive for three drugs used in the treatment of hypertension, none of the medications should have been impairing and were unlikely to have contributed to the accident.

Probable cause

The pilot's failure to maintain airplane control due to the airplane’s exceedence of its maximum gross weight and center of gravity’s most rearward limit and his lack of familiarity with the airplane make and model, which resulted in an aerodynamic stall and subsequent spin. Contributing to the accident was the pilot's decision to knowingly operate the airplane over the maximum allowable gross weight with reduced longitudinal stability.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA12FA326
Event ID
20120509X31107
Case number
ERA12FA326
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. 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: ea79ba405d9f37ea66231b0e9aef046fae9ff5f163813241b241cb70d1df588b; retrieved 2026-09-13T22:21:07.064Z.