FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ANC25LA007 · Aviat A1 B

27 Oct 2024 · Seward, AK, United States Narrative disagrees

Aviat A1 B · Accident: abnormal runway contact during landing

From Merrill Field (PAMR) to Seward, AK

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
ANC25LA007
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
Event fatalities
Unknown
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 A1 B

Aircraft type
Aviat A1
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
N307AM
Operator
Unknown
Onboard fatalities
Unknown
Route
From Merrill Field (PAMR), Anchorage, AKTo Seward, AK
Aircraft age
About 17 years (built 2007)
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
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
Abnormal runway contact
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 as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The pilot reported that, while conducting stop-and-go landings on a beach in his tailwheel-equipped airplane, he flared early which resulted in a hard landing. The pilot lost directional control of the airplane and subsequently nosed over and came to rest inverted resulting in substantial damage to the wings, lift struts, rudder, and vertical and horizontal stabilizers. The pilot reported that there were no preaccident mechanical failures or malfunctions with the airplane that would have precluded normal operation.

Probable cause

The pilot’s improper landing flare which resulted in a hard landing, loss of directional control, and nose-over.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ANC25LA007
Event ID
20241028195386
Case number
ANC25LA007
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, cause areas. 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: eae4069c2e87d361ce7ff91924d1708ec3edcf087484be913c779d57def7268c; retrieved 2026-09-16T19:25:07.722Z.