eFlight
Accidents · NTSB WPR12LA324 · Final report

Hawker Beechcraft G58 accident near Medford, Oregon, July 20, 2012

On July 20, 2012 at about 6:45 pm local time, a 2011 Hawker Beechcraft G58, registered N7122T, was substantially damaged in an accident during landing (landing roll) near Medford, Oregon (Rogue Valley Intl-Medford airport). It was a personal flight under general aviation rules (Part 91). No one was hurt; 2 people were on board or involved. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

A loss of directional control on landing for reasons that could not be determined based on the available evidence.

Source: NTSB aviation accident database, copy made November 2, 2026. Docket and reports at the NTSB.

What the record shows

Date
July 20, 2012 · about 6:45 pm local time · cases in 2012
Place
Medford, Oregon · Rogue Valley Intl-Medford · cases near this airport · map
Type
Accident
Injuries
No one was hurt; 2 people were on board or involved.
Weather
visual conditions (good weather)
Aircraft
Hawker Beechcraft G58, built 2011
Registration
N7122T · no longer on the register · serial TH-2325
Damage
Substantial damage
Flight
Personal flight · general aviation rules (Part 91)

The NTSB's narrative final · quoted from the NTSB record

The owner/pilot reported that all aspects of the personal cross-country flight were uneventful until touchdown when the airplane immediately experienced directional control issues. The airplane subsequently veered off the right side of the runway and struck a sign and a ditch before it came to rest. All three landing gear were fracture-separated from the airplane during the accident sequence. The right and left main landing gear torque links exhibited different damage patterns. None of the attachment hardware for the left torque link knee joint was located. The lack of any landing gear operating anomalies during the accident flight's taxi, takeoff, gear retraction, and gear extension sequences, combined with the damage patterns to the left main landing gear torque links, were consistent with the knee joint attachment bolt being present through at least the beginning of the failure sequence on landing and with the bolt being at least partially installed during the landing. Further, the available evidence did not indicate that a pre-existing mechanical failure of the knee joint bolt had occurred. For the bolt to partially back out of its proper position, the retaining nut would have to be missing either due to the cotter key being lost as a result of mechanical failure or absent because it was never installed. If the cotter key was damaged or the nut was improperly torqued, it is possible that multiple taxi, takeoff, and landing cycles could have damaged and eventually caused the cotter key, the nut, or the bolt to fail, but no evidence was found to support that scenario. The two mechanics who repaired the left main landing gear strut 7 months before the accident reported that the cotter key was installed during the repair. Although the pilot asserted that the cotter key was never installed, he and another pilot had completed 32 flights, not including the accident flight, in the airplane since that time, thus, providing 33 opportunities to detect its absence during their respective preflight inspections, yet neither did so. In addition, those flights were accomplished after renewed attention to the left main landing gear because of the strut repair; however, neither pilot noted any missing hardware. Based on the available evidence, which did not include the attachment hardware, the underlying reason for the loss of directional control could not be determined.

The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.

The factual record from the NTSB's investigation tables, in plain English

What happened, in order

  1. Loss of control on ground during landing
  2. Runway excursion during landing (landing roll) defining event
  3. Collision with terrain or object (not controlled flight into terrain) during landing (landing roll)

The NTSB's findings

  • Aircraft › Aircraft systems › Landing gear system › Main landing gear › Failure other cases naming the landing gear
  • cause Not determined › Not determined › (general) › (general) › Unknown/Not determined
  • cause Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Directional control › Not attained/maintained

Pilot

  • Certificate: private
  • Ratings: multi-engine land; instrument: airplane
  • Flight time: 864 hours in all; 45 in this make and model; 28 in the last 90 days; 7 in the last 30 days; 850 as pilot in command
  • Last flight review: December 9, 2011
  • Medical certificate: Class 3 (with waivers/limitations)
  • Seat: left
  • Injury: no injuries

The aircraft

  • Airframe total time: 54 hours
  • Seats: 6
  • Landing gear: retractable
  • Engine 1: Continental IO-550 (piston); 54 hours total
  • Engine 2: Continental IO-550 (piston); 54 hours total

The flight

  • Departed from: PSP Palm Springs CA at 3:39 pm
  • Destination: MFR Medford OR
  • Flight plan: IFR
  • Runway 32, 8,800 ft by 150 ft

Weather at the time

  • Light: daylight
  • Wind: at 4 knots
  • Visibility: 10 statute miles
  • Sky: clear
  • Temperature: 75°F (24°C), dew point 54°F (12°C)
  • Altimeter: 30.14 inHg
  • Observation at 6:53 pm from MFR

Injuries

FatalSeriousMinorNone
Flight crew1
Passengers1

Documents from the investigation the NTSB's docket: the evidence folder behind the report

23 documents, released by the NTSB on February 10, 2015. View them here, or download them; the NTSB redacts some personal details before release, and this site shows the NTSB's own titles rather than its file names.

#DocumentWhat it is
1 Pilot/operator Aircraft Accident Report, NTSB Form 6120.1 PDF, 9 pages View Download
2 Kmfr Report PDF, 2 pages View Download
3 On Scene Information PDF, 12 pages View Download
4 Pilot Provided on Scene Information PDF, 4 pages View Download
5 Record of Communication - Airport Operations Manager PDF, 1 page View Download
6 Record of Communication – Location Measurements PDF, 1 page View Download
7 Record of Conversation – Pilot July 25 PDF, 1 page View Download
8 Record of Communication – Pilot July 27 PDF, 1 page View Download
9 Record of Communication – Pilot July 31 PDF, 2 pages View Download
10 Record of Conversation – Pilot August 17 PDF, 1 page View Download
11 Record of Communication – Pilot August 17 PDF, 1 page View Download
12 Pilot Email Veeroff Explanation PDF, 1 page View Download
13 Email Record of Communication Pilot PDF, 1 page View Download
14 Record of Conversation – Owner Palm Springs Aircraft Maintenance PDF, 2 pages View Download
15 Record of Conversation – Palm Springs Aircraft Maintenance Mechanic PDF, 2 pages View Download
16 Record of Communication Hbc Maintenance Chronology PDF, 1 page View Download
17 Maintenance Record PDF, 1 page View Download
18 Palm Springs Aircraft Maintenance Invoice PDF, 1 page View Download
19 Record of Communication – Hbc Air Safety Manager PDF, 2 pages View Download
20 Hbc Email re Bolt Failure PDF, 1 page View Download
21 Metars PDF, 1 page View Download
22 Release of Aircraft Wreckage, NTSB Form 6120.15 PDF, 3 pages View Download
23 Materials Laboratory 15 - Factual Report 12-144 PDF, 5 pages View Download

The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.

Connections how this case links to the rest of the register

Aircraft
Place

The whole map of how records connect · these connections as data: /graph/accident/WPR12LA324.json.

The bigger picture in Aviation Analytics: accidents over time since 1982, by model, by phase of flight and conditions, by place and on the map.

Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text does not name anyone involved, its policy at this time. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.

Aircraft

By kindModelsMakersEnginesFleetsWhat changed

Fly

Plan a flightAirportsLive mapRoutes and flightsFuels

Training and work

TrainingFlight schoolsGround schoolsPilot examinersMedical examinersJobs

Companies

DirectoryCharter operatorsFBOsRepair stationsClaim your listing

Safety and data

AccidentsRecords checkAnalyticsSAFxCHANGEThe graphAbout

Colours follow your device's light or dark setting.