SEA05LA134 · Jones Long EZ
Jones Long EZ · Accident: loss of control in flight on approach
From Caldwell Executive Airport (EUL) to Sunrise Skypark Airport (ID40)
Event
- NTSB case
- SEA05LA134
- 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
Jones Long EZ
- Aircraft type
- Jones LONG EZ
- 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
- N58LD
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Caldwell Executive Airport (EUL), Caldwell, IDTo Sunrise Skypark Airport (ID40), Marsing, ID
- 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 · VFR pattern final
- 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
- 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 › Airspeed, not maintained
- Pilot in command › Recovery from bounced landing, delayed
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 was performing a landing, and as he crossed the end of the runway he slowed the airplane and then stalled it. The passenger said that "he felt the bottom drop out and he knew they were going to bounce." He said that the airplane landed hard, and bounced up and drifted to the left. When it came down the second time, the left main wheel was off the runway in soft dirt, further pulling the airplane left. He said the pilot applied power "in an attempt to go around." Subsequently the airplane struck a perpendicular taxiway with a drainage culvert through it, which separated the main landing gear from the fuselage. The airplane proceeded forward and struck a second taxiway, badly damaging the nose of the fuselage. The pilot was fatally injured.
Probable cause
The pilot's failure to maintain airspeed during landing, and his subsequent delay in attempting a recovery from a bounced landing. A contributing factor was the taxiway berm.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record SEA05LA134
- Event ID
- 20050630X00913
- Case number
- SEA05LA134
- 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: cbebd876ba5c29c9102d0fabe286eb4e217eb552b240909037046bfe444dedd0; retrieved 2026-09-20T17:59:57.582Z.