FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

LAX08CA208 · Pipistrel Virus 912

1 Jul 2008 · Bend, OR, United States

Pipistrel Virus 912 · Accident: loss of control on ground during landing

From Sunriver Airport (S21) to Bend Municipal Airport (BDN)

Report a problem

Event

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

Pipistrel Virus 912

Aircraft type
Pipistrel VIRUS 912
Category
Glider
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
N126BF
Operator
Unknown
Onboard fatalities
Unknown
Route
From Sunriver Airport (S21), Sunriver, ORTo Bend Municipal Airport (BDN), Bend, 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 · flare/touchdown
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
Loss of control on ground
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 › Action/decision

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

The pilot was performing an approach to the destination airport in his powered glider. The aircraft touched down and bounced. It then began to veer to the right of the runway centerline. The aircraft then swerved to the left and the pilot could not regain control. The aircraft continued off the runway surface and down an embankment. The main landing gear encountered soft terrain and the aircraft nosed over. The pilot stated that there were no preimpact mechanical failures or malfunctions with the airframe or engine. He noted that winds were calm. When queried as to the cause of the accident, the pilot opined that the aircraft had "too much energy" during the landing sequence.

Probable cause

The pilot's improper flare, inadequate bounced landing recovery, and his failure to maintain directional control.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record LAX08CA208
Event ID
20080916X01475
Case number
LAX08CA208
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: 735e2eb2a6eebdb627224ac2b1f0b2e8d3553432b7e9fc7003233248468262b4; retrieved 2026-09-15T10:13:47.671Z.