The U.S. aircraft register, updated daily
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 October 5, 2026. Docket and reports at the NTSB.

What the record shows

Date
July 20, 2012 · about 6:45 pm local time
Place
Medford, Oregon · Rogue Valley Intl-Medford · 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
  • 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

The docket, the folder of records gathered during an investigation (maintenance records, photographs, witness statements, examinations), has not been read from the NTSB for this case yet; the list appears here once it has. Open the docket at the NTSB.

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 never names anyone involved. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.