FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

SEA01LA074 · Aviat A-1B

17 Apr 2001 · Hagerman, ID, United States

Aviat A-1B · Accident: in flight collision with object on approach

From Friedman Memorial Airport (SUN) to Hagerman, ID

Report a problem

Event

NTSB case
SEA01LA074
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
N440PS
Operator
Unknown
Onboard fatalities
Unknown
Route
From Friedman Memorial Airport (SUN), Hailey, IDTo Hagerman, 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 go-around
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
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 › Proper alignment, not maintained

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The pilot stated that his final approach to his private airstrip was to the east. He stated that upon touchdown, he felt he was a little too fast so he executed a go-around. He stated that upon rotation, he began drifting left and struck a small windsock at the east end of the airstrip with the airplane's left wing tip. The pilot stated that the airplane then spun left and struck the ground "flat" and dug its right wing tip into the dirt. The pilot stated that no mechanical malfunction or failure was involved in the accident, and that winds were calm. The pilot reported that his airstrip was 1,000 feet long.

Probable cause

The pilot's failure to maintain proper runway alignment during an attempted go-around, resulting in an inflight collision with a wind sock. Factors were a short runway/landing area condition, the pilot's excessive airspeed on final approach, and the wind sock.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record SEA01LA074
Event ID
20010420X00785
Case number
SEA01LA074
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. 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: 47568affd252ba3134d38f776b56f4748edfc40339ca6af085e80c0500fa60b8; retrieved 2026-09-22T12:01:48.736Z.