ANC11LA041 · Eclipse Aviation Corp EA500
Eclipse Aviation Corp EA500 · Accident: landing gear not configured
From Ugolny Yuri Ryktheu Airport (UHMA) to Nome Airport (PAOM)
Event
- NTSB case
- ANC11LA041
- 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
Eclipse Aviation Corp EA500
- Aircraft type
- Eclipse EA500
- 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
- N168TT
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Ugolny Yuri Ryktheu Airport (UHMA), AnadyrTo Nome Airport (PAOM), Nome, AK
- 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
- Landing · flare/touchdown
- 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, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The pilot indicated that, prior to the accident flight, the wing flaps had failed, but he decided to proceed with the flight contrary to the Airplane Flight Manual guidance. While conducting a no-flap approach to the airport, he decided that his airspeed was too fast to land, and he initiated a go-around. During the go-around, the airplane continued to descend, and the fuselage struck the runway. The pilot was able to complete the go-around, and realized that he had not extended the landing gear. He lowered the landing gear, and landed the airplane uneventfully. He elected to remain overnight at the airport due to fatigue. The next day, he decided to test fly the airplane. During the takeoff roll, the airplane had a severe vibration, and he aborted the takeoff. During a subsequent inspection, an aviation mechanic discovered that the center wing carry-through cracked when the belly skid pad deflected up into a stringer during the gear-up landing.
Probable cause
The pilot landed without lowering the landing gear. Contributing to the accident was the pilot's decision to fly the airplane with an inoperative wing flap system.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ANC11LA041
- Event ID
- 20110609X31548
- Case number
- ANC11LA041
- 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: local date, investigation status, coordinates. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2011-06-02.
- API snapshot SHA-256: 4f7ca80e8ccba5a8f944300577f8bc9ee0a3dbe633d30a6bd7d3887c95ccf662; retrieved 2026-09-15T16:15:51.138Z.