FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CHI05LA030 · Hedge Bede-4

13 Nov 2004 · Omaha, NE, United States

Hedge Bede-4 · Accident: loss of control in flight on approach

From North Omaha Airport (3NO) to an unrecorded destination

Report a problem

Event

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

Hedge Bede-4

Aircraft type
Hedge BEDE-4
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
N435BD
Operator
Unknown
Onboard fatalities
Unknown
Route
From North Omaha Airport (3NO), Omaha, NETo 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
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/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

  • Pilot in command › Aircraft control, not maintained
  • Pilot in command › Airspeed, low

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 was substantially damaged when it impacted terrain following a stall/spin while on approach to land. A witness reported he saw the airplane flying low in a southerly direction. He stated that he heard a loud noise and saw the airplane spiraling toward the ground, subsequently impacting the ground nose first. The accident site was located approximately 540 feet north of the approach end of runway 17. The airplane was oriented on a 040-degree magnetic heading. Debris was confined to the area immediately surrounding the aircraft. No impact marks in the terrain except for those in the immediate vicinity of the aircraft were observed. An individual who knew the accident pilot reported that he had the tendency to make "flat, skidding" turns, with little or no bank angle. A post-accident examination of the airframe and engine did not reveal any evidence of a pre-impact anomaly. Flight control continuity was verified from the control surfaces to the cabin area.

Probable cause

The pilot's failure to maintain control of the airplane resulting in a stall and spin, while on approach to land. Contributing factors were the airplane's low altitude and low airspeed at the time of loss of control.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CHI05LA030
Event ID
20041118X01839
Case number
CHI05LA030
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: cd2946802828273dc3905e3959712c67c8bf704074ccd06d698b4d1b6a57d3be; retrieved 2026-09-20T18:12:11.184Z.