FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR12CA363 · Silvaire LUSCOMBE 8E

19 Aug 2012 · Hillsboro, OR, United States

Silvaire LUSCOMBE 8E · Accident: nose over/nose down during landing

From Stark's Twin Oaks Airpark (7S3) to Stark's Twin Oaks Airpark (7S3)

Report a problem

Event

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

Silvaire LUSCOMBE 8E

Aircraft type
Silvaire LUSCOMBE 8
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
N2287K
Operator
Unknown
Onboard fatalities
Unknown
Route
From Stark's Twin Oaks Airpark (7S3), Hillsboro, ORTo Stark's Twin Oaks Airpark (7S3), Hillsboro, OR
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
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
Nose over/nose down
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 systems
  • Personnel issues › Task performance

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

NTSB narrative

The purpose of the flight was for the pilot to practice landing his tailwheel-equipped airplane on a grass airstrip. After departure, he remained in the airstrip’s traffic pattern and configured the airplane for a wheel landing. During the landing roll, with the airplane’s main landing gear on the grass and the tailwheel still airborne, the pilot applied brake pressure. The airplane nosed over, sustaining substantial damage to the firewall. The pilot reported that there were no preaccident mechanical malfunctions or failures that would have precluded normal operation.

Probable cause

The pilot’s improper use of the brakes during the landing roll, which resulted in a nose over.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR12CA363
Event ID
20120821X31159
Case number
WPR12CA363
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. 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: 61ceef38e07a217471d798e4519940aa84705fba285320e61fe701c5c53c6423; retrieved 2026-09-15T19:27:35.623Z.