DFW07LA170 · Hazen Fly Baby
Hazen Fly Baby · Accident: in flight collision with object
From Big Cedar, OK (no airport) to M39 · Mena, AR
Event
- NTSB case
- DFW07LA170
- 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
Hazen Fly Baby
- Aircraft type
- Hazen FLY BABY
- 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
- N6156Y
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Big Cedar, OK (no airport)To M39 · Mena, AR
- 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
- Unknown
- 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
- In flight collision with object
- 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
- Tree(s)
- 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
- Reason for occurrence undetermined
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The private pilot was flying cross country in his single-engine homebuilt airplane when it collided with wooded and mountainous terrain in day visual meteorological conditions for undetermined reasons. The airplane was missing for five days before it was located by units of the Civil Air Patrol at an elevation of 2,950 feet mean sea level. A Federal Aviation Administration (FAA) inspector performed an on-scene examination on the day the airplane wreckage was located. According to the inspector, the airplane, which was constructed from wood and fabric frame, came to rest at the base of several large pine trees and did not burn. The initial impact point appeared to be the tops of the trees located directly above the main wreckage, which included the engine, fuselage, both wings, and tail section. All flight control surfaces remained attached to the airframe. The two-bladed wooden propeller was damaged; however, it remained attached to the engine. Engine continuity was established via manual rotation of the propeller. The single fuel tank was breached from impact forces, and the fuel cap was found secured to the tank. No anomalies were found with the airframe or engine that could have prevented normal operation. The pilot held a private pilot certificate for airplane single-engine land and also held an inspection certificate for experimental aircraft. His last FAA third class medical certificate was issued on August 1, 2003. At that time, the pilot reported having accumulated a total of 452 flight hours. The pilot's logbook and the airplane's maintenance records were not located during the course of the investigation.
Probable cause
The airplane's collision with wooded and mountainous terrain for undetermined reasons.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record DFW07LA170
- Event ID
- 20070730X01062
- Case number
- DFW07LA170
- 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: b9a191105a6f1da94a5a48e79ea02a3a6407221ab26e6e4899d42b85f9ac7cc1; retrieved 2026-09-20T16:27:40.450Z.