FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

SEA08CA212 · Sport Flight International Astra S-2

27 Sept 2008 · Spokane, WA, United States

Sport Flight International Astra S-2 · Accident: nose over/nose down during landing

From Felts Field (SFF) to Felts Field (SFF)

Report a problem

Event

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

Sport Flight International Astra S-2

Aircraft type
Sport Flight ASTRA
Category
Weight-Shift
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
N3115C
Operator
George L Balazs · private individual
Onboard fatalities
Unknown
Route
From Felts Field (SFF), Spokane, WATo Felts Field (SFF), Spokane, WA
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 › Action/decision
  • Personnel issues › Task performance

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

NTSB narrative

The pilot reported that during the landing roll and after applying brakes, he encountered a left/right oscillation that increased in intensity as he tried to correct with nose wheel steering. The pilot further reported that before he could get the airplane stopped it tipped over, impacting the runway surface with its nose cone and left wing. The pilot reported to a Federal Aviation Administration aviation safety inspector that the day before the accident he had replaced the two rear wheel brake pads with new ones and was warned not to apply the new brakes too heavily, or a loss of control might occur. The pilot revealed to the inspector that he applied more brakes than he should have during the landing roll. The pilot reported 19 hours flight time in make and model.

Probable cause

The pilot's excessive use of brakes and failure to maintain directional control during the landing roll.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record SEA08CA212
Event ID
20081017X52811
Case number
SEA08CA212
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: c90246130fca7d9e115b1d94b7256cd76088898ed279f96212459bcd7309407e; retrieved 2026-09-15T10:28:53.982Z.