29 Jun 2013: SCHWEIZER AIRCRAFT CORP G-164B — Airworks LLC

29 Jun 2013: SCHWEIZER AIRCRAFT CORP G-164B (N3633S) — Airworks LLC

No fatalities • Jackson, TN, United States

Probable cause

A failure of the right main landing gear wheel rim during the landing roll, resulting in a loss of control and a subsequent collapse of the right main landing gear.

— NTSB Determination

Accident narrative

On June 29, 2013, about 0645 central daylight time, a Schweizer Aircraft Corp. G-164B, N3633S, was substantially damaged during a landing gear collapse while landing at McKellar-Sipes Regional Airport (MKL), Jackson, Tennessee. The commercial pilot was not injured. Visual meteorological conditions prevailed, and no flight plan was filed for the local aerial application flight, which was conducted under the provisions of Title 14 Code of Federal Regulations (CFR) Part 137.

At the conclusion of the aerial application flight, the pilot was returning to the departure airport. The pilot touched town on runway 2 at MKL utilizing a full-stall landing technique, and shortly thereafter, the airplane began drifting to the right. The pilot responded by applying left aileron, rudder, and brake; and as the airplane returned to the centerline, the pilot attempted to realign the airplane's direction of travel with the runway. The control inputs were ineffective, and the pilot next applied full reverse thrust and attempted to apply the brakes. The pilot noted that the application of left brake would turn the airplane further left and that the right brake was unresponsive.

The airplane continued to drift left and the right main landing gear leg collapsed. Following the accident, the pilot found that the right main landing gear wheel had broken away from its axle at the hub. Fractured portions of the wheel were later recovered from the runway.

According to Federal Aviation Administration (FAA) airworthiness records, the airplane was manufactured in March 1986. On January 6, 2012, the registered owner of the airplane submitted a request to the FAA for a replacement airworthiness certificate. According to the request letter, the aircraft logs were "burned in a hangar fire." Airframe logs covering a period between May and December 2012 were examined. An annual inspection was completed on May 20, 2012, and the maintenance log entry for the inspection stated in-part, "Wheels and brakes checked-OK." Another annual inspection was completed on December 12, 2012, and the maintenance log entry for the inspection detailed a lubrication of the landing gear wheel bearings and replacement of the brake pads. No subsequent maintenance log entries detailed any maintenance or inspection of the landing gear.

The wheel rim and bearing hub assembly were submitted to the NTSB Materials Laboratory for detailed examination. The rim was of the split design with bearing bores in the centers of each rim half and a cylindrical spacer sleeve positioned between the rim halves and concentric to the bearing bores when installed on the axle stub. The center section of each rim half, which contained the bearing bores, had broken into multiple pieces and separated from the periphery of its respective rim half. A portion of the outboard rim half's periphery was also fractured and separated into multiple pieces. Some portions of the rim were not recovered from the accident scene. Examination of the fracture surfaces on the outboard and inboard rims, along with portions of the center section pieces of each rim half identified only overstress fractures and no evidence of preexisting damage. Some fracture surfaces were smeared from contact forces and could not be evaluated. Examination of the bolts securing the two halves of the rim and their associated nuts and washers did not reveal any unusual characteristics.

The owner of the airplane reported that he had entered into a verbal contract with the operator in June 2013, and that the owner was to provide an aircraft, pilot, and aircraft insurance; while the operator would provide the fuel, agricultural application work to be performed, and CFR Part137 certificate, as well as direct the use of the airplane. The operator relayed a similar understanding of the verbal arrangement; however, the operator stated that the airplane would be operating under a CFR Part 137 certificate provided by the owner. Review of FAA records showed that the airplane owner did not hold a CFR Part 137 operating certificate. Additionally, the accident airplane was not one of the aircraft listed on the operator's CFR Part 137 operating specifications.

Contributing factors

  • cause Wheel/ski/float — Failure

Conditions

Weather
VMC, wind 260/04kt, vis 10sm

Loading the flight search…

What you can do on Flight Finder

  • Search flights between any two airports with live fares.
  • By aircraft — pick a plane model (e.g. Boeing 787, Airbus A350) and see every route it flies from your origin.
  • Route map — click any airport worldwide to explore its destinations, or draw a radius to find nearby airports.
  • Global aviation safety — aviation accident database, 5,200+ records since 1980, with map and rankings by aircraft and operator.
  • NTSB safety feed — recent U.S. aviation accidents and incidents from the official NTSB CAROL database, updated daily.

Frequently asked questions

How do I search flights by aircraft type on FlightFinder?

Pick an aircraft model — Boeing 737, Airbus A320, A380, Boeing 787 Dreamliner and more — enter your origin airport, and FlightFinder shows every route that plane flies from there with live fares.

Which aircraft types can I filter by?

We support Boeing 737/747/757/767/777/787, the full Airbus A220/A319/A320/A321/A330/A340/A350/A380 family, Embraer E170/E175/E190/E195, Bombardier CRJ and Dash 8, and the ATR 42/72 turboprops.

Is FlightFinder free to use?

Search and schedules are free. Pro ($4.99/month, $39/year, or $99 one-time lifetime) unlocks the enriched flight card — on-time stats, CO₂ per passenger, amenities, live gate & weather — plus My Trips with push alerts.

Where does the route data come from?

Live schedules come from Amadeus, AeroDataBox and Travelpayouts. Observed routes (which aircraft actually flew a given city pair) are crowdsourced from adsb.lol ADS-B data under the Open Database License.