ERA26LA030 · Hugh Nunnally Farrior COZY MK IV
Hugh Nunnally Farrior COZY MK IV · Accident: landing gear not configured
From Athens Ben Epps Airport (AHN) to Tampa Executive Airport (VDF)
Event
- NTSB case
- ERA26LA030
- 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
- 0
- 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
Hugh Nunnally Farrior COZY MK IV
- Aircraft type
- Hugh Nunnally Farrior COZY MK
- 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
- N222HF
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Athens Ben Epps Airport (AHN), Athens, GATo Tampa Executive Airport (VDF), Tampa, FL
- Aircraft age
- About 1 year (built 2024)
- 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
- Landing
- 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
- Landing gear not configured
- 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 systems
- Personnel issues › Action/decision
Approximate · Coordinates from the NTSB case API, not marked as estimated; no uncertainty radius is established.
NTSB narrative
The pilot and builder of the experimental airplane reported that in cruise flight about 1,700 ft above ground level, he felt a vibration that progressively intensified. He elected to make a precautionary landing at a nearby airport; however, he forgot to extend the nose landing gear, and the airplane’s nose contacted the runway surface during landing, which resulted in substantial damage to the lower fuselage. Post accident examination revealed that the composite propeller had shed a portion of its nickel-plated leading edge and exhibited damage consistent with delamination. Further examination by the propeller manufacturer revealed that the delamination was the result of heat damage and a total failure of the propeller was imminent. About 5 months before the accident, the pilot contacted the propeller manufacturer and provided photographs that revealed early stage delamination damage to the propeller. He was advised by several company representatives that the damage was the result of heat due to the location and proximity of the engine exhaust to the propeller, and that he should not continue to fly with that propeller.
Probable cause
The pilot’s failure to extend the nose landing gear, which resulted in a nose gear up landing. Contributing to the accident was the pilot’s inappropriate decision to continue to fly with known delamination damage to the propeller.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA26LA030
- Event ID
- 20251104201951
- Case number
- ERA26LA030
- 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, cause areas. 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: 2e4612909e0e418c9632adcc3cdb412f15fd924d6f0bc899cbbbf76da08bc1e7; retrieved 2026-09-16T20:31:10.408Z.