FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR13CA280 · Aviat Aircraft Inc A-1A

21 Jun 2013 · McCall, ID, United States Possible conflict

Aviat Aircraft Inc A-1A · Accident: aerodynamic stall/spin on approach

From McCall Municipal Airport (MYL) to McCall Municipal Airport (MYL)

Report a problem

Narrative check · The NTSB narrative appears to contradict this record's location. Values are shown as recorded, not corrected; compare with the narrative.

Event

NTSB case
WPR13CA280
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 Aircraft Inc A-1A

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
N26HV
Onboard fatalities
Unknown
Route
From McCall Municipal Airport (MYL), McCall, IDTo McCall Municipal Airport (MYL), McCall, 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
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
Aerodynamic stall/spin
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 oper/perf/capability
  • Personnel issues › Task performance

Approximate · Coordinates from the NTSB case API, not marked as estimated; no uncertainty radius is established.

NTSB narrative

The pilot reported that the purpose of the flight was to practice landings with a certified flight instructor at various back country airstrips. After three uneventful landings, the pilot circled over a fourth landing strip and noted that she needed to maintain the airplane’s minimum approach airspeed to be able to land on the short runway; she then entered the traffic pattern. While on short final, about 25 feet above the ground, the airplane stalled and started to descend. The pilot added power; however, the airplane subsequently landed hard and sustained substantial damage to the left wing. The pilot reported no mechanical failures or malfunctions with the airframe or engine that would have precluded normal operation.

Probable cause

The pilot’s failure to maintain adequate airspeed while on approach for landing, which resulted in a loss of airplane control and a hard landing.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR13CA280
Event ID
20130622X44621
Case number
WPR13CA280
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. 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: 1e0d6d5be40bcfd7ed95a710511bfdaa3c2e2b76d591ca3180fd54f2f5de3f2f; retrieved 2026-09-15T21:59:01.398Z.