FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

SEA04LA028 · Aviat A-1B

17 Dec 2003 · Hailey, ID, United States

Aviat A-1B · Accident: loss of control on ground/water during landing

From Jerome County Airport (JER) to Friedman Memorial Airport (SUN)

Report a problem

Event

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

Aviat A-1B

Aircraft type
Aviat A-1
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
N290AM
Operator
Unknown
Onboard fatalities
Unknown
Route
From Jerome County Airport (JER), Jerome Airport, IDTo Friedman Memorial Airport (SUN)
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 · landing roll
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 on ground/water
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 › Directional control, not maintained

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

After landing on runway 13, the airplane initially veered to the left during its landing roll. The pilot then overcorrected to the right using too much right brake, and then overcorrected back to the left. This resulted in the right wing rising, the left main gear collapsing, and the left wing striking the runway surface. The airplane continued its rotation to the left, eventually coming to rest in an upright position. The pilot reported the wind at the time of the accident as being variable at 4 knots, while the local weather observation facility at the airport reported the wind being calm.

Probable cause

The pilot's failure to maintain directional control of the airplane during the landing roll, which resulted in an inadvertent group loop and the collapse of the right main landing gear.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record SEA04LA028
Event ID
20031222X02076
Case number
SEA04LA028
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: 3da80dc285e990f98dba4a65de2730937d83ba8fc2582f9b3bdaaad8a62c2a73; retrieved 2026-09-22T08:04:25.008Z.