FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR12LA104 · Beech G18 S

14 Feb 2012 · Hollister, CA, United States

Beech G18 S · Accident: abnormal runway contact during landing

From CHV · Hollister, CA to CHV · Hollister, CA

Report a problem

Narrative check · The NTSB narrative appears to contradict this record's departure or destination. Values are shown as recorded, not corrected; compare with the narrative.

Event

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

Beech G18 S

Aircraft type
Beechcraft 18
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
VH-NWB
Operator
Unknown
Onboard fatalities
Unknown
Route Narrative disagrees
From CHV · Hollister, CATo CHV · Hollister, CA
Aircraft age
About 52 years (built 1960)
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
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 was preparing the airplane for a transpacific flight. The day before the accident, he conducted two test flights, and he noted that, during each flight, the oil temperature for the right engine was slightly higher than expected but that it remained within normal operating limitations. On the day of the accident, he decided to perform another test flight and brought a mechanic to assist with identifying any engine issues. The pilot reported that, just after liftoff, the airplane's right wing dropped, which he believed was due to a loss of right engine power. The pilot decided to reduce the left engine's power in an attempt to return the airplane to a wings-level attitude. The airplane then rolled left and pitched nose down. The airplane landed hard in a left-wing-low attitude, and the left main landing gear tire ruptured. The pilot was unable to maintain directional control of the airplane, which subsequently ground looped, departed the runway surface, and came to rest in a ditch. The airplane sustained substantial damage to the left wing tip and aileron.

The mechanic-passenger reported that the pilot did not align the airplane with the runway centerline during the takeoff, and, as a result, when the tailwheel lifted, the airplane veered left. As the pilot attempted to realign the airplane with the runway centerline, the airplane became airborne in a left-wing-high configuration. The airplane lifted off and began to climb and then the nose and left wing dropped. The mechanic reported no mechanical malfunctions or failures to the right engine that would have precluded normal operation. It is likely that the pilot, in attempting to maintain runway alignment and a wings-level attitude, failed to maintain adequate airspeed, which resulted in an aerodynamic stall.

Probable cause

The pilot’s failure to maintain adequate airspeed during the initial climb, which resulted in an aerodynamic stall and a subsequent hard landing, loss of directional control, and ground loop.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR12LA104
Event ID
20120214X10923
Case number
WPR12LA104
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: 25b7ed93e801a1ce8bf619c9ce6ff580825c80b369b8f43e24e7556ae1705ec3; retrieved 2026-09-15T17:14:18.163Z.