FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ANC08CA022 · Aeronca 7JC

28 Nov 2007 · Wasilla, AK, United States

Aeronca 7JC · Accident: nose over during landing

From Birchwood Airport (PABV) to Wasilla Airport (PAWS)

Report a problem

Event

NTSB case
ANC08CA022
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
Instrument Meteorological Cond

Aeronca 7JC

Aircraft type
Aeronca 7
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
N8965R
Operator
Unknown
Onboard fatalities
Unknown
Route
From Birchwood Airport (PABV), Chugiak, AKTo Wasilla Airport (PAWS), Wasilla, AK
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
Nose over
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 › Brakes(normal), excessive

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

NTSB narrative

The private certificated pilot was landing a tundra tire, and tailwheel-equipped airplane on an asphalt surfaced runway during a Title 14, CFR Part 91, personal flight. During the landing roll, he reported that he applied the brakes and the airplane nosed over. The airplane received structural damage to the wings and the vertical stabilizer. In the Pilot/Operator Aircraft Accident Report (NTSB Form 6120.1) submitted by the pilot, he indicated that there was no mechanical malfunction with the airplane. In the optional safety recommendation portion of the form, (How could this accident have been prevented?), the pilot stated in part: "maybe longer roll."

Probable cause

The pilot's excessive application of the airplane's brakes during the landing roll, which resulted in a nose-over.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ANC08CA022
Event ID
20071212X01936
Case number
ANC08CA022
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: 0dc57691c64b5c586286a9c69dd0faacd4ec4913cb84b22a9b270e624503bef6; retrieved 2026-09-22T03:15:34.747Z.