Cessna 150 accident near Pottsville, Pennsylvania, October 22, 2017
On October 22, 2017 at about 10:15 pm local time, a 1967 Cessna 150, registered N22092, was substantially damaged in an accident near Pottsville, Pennsylvania (Schuylkill County /Joe Zerbey 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
The failure of the right rudder cable and subsequent loss of directional control during landing.
Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- October 22, 2017 · about 10:15 pm local time
- Place
- Pottsville, Pennsylvania · Schuylkill County /Joe Zerbey · map
- Type
- Accident
- Injuries
- No one was hurt; 2 people were on board or involved.
- Weather
- visual conditions (good weather)
- Aircraft
- Cessna 150 H, built 1967 · all 150s on the register
- Registration
- N22092 · no longer on the register · serial 15068059
- Damage
- Substantial damage
- Flight
- Personal flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
The pilot reported that, during approach, the automatic weather observation station at the destination airport reported that the wind was from 170° at 12 knots. He added that there was "very massive choppy wind, including what could have been windshear, updrafts, and downdrafts." During the landing roll on runway 11, a wind gust blew the airplane off the runway to the left. The pilot attempted to recover, but the airplane impacted a ditch. The airplane sustained substantial damage to the fuselage and right wing. The pilot reported that there were no preaccident mechanical failures or malfunctions with the airplane that would have precluded normal operation. The Federal Aviation Administration (FAA) inspector reported that a postaccident examination revealed that the rudder cable that passed along the left side of the fuselage was separated into three pieces. The rudder cable was covered in debris, which contained red fibers. The rudder cable was splayed and exhibited signatures consistent with tension overload. The airplane's illustrated parts catalog contained a diagram titled, "Rudder Control System Installation," which displayed the cable along the left side of the fuselage cross over the right side of the airplane, in the tailcone section, and connect to the right side of the rudder horn, which provided right rudder authority. The airplane's most recent inspection was an annual, which was conducted 6 months before the accident flight. The FAA inspector interviewed the mechanic who performed the most recent annual inspection, and the mechanic reported that, during inspections, he used manufacturer data and FAA Advisory Circular, AC 43.13-1B, "Acceptable Methods, Techniques, and Practices – Aircraft Inspection and Repair." He further reported, multiple times, that he should probably "tighten up" his inspections. AC 43.13-1B contained a section titled, "Cable System Inspection," which stated the following: "Aircraft cable systems are subject to a variety of environmental conditions and deterioration. Wire or strand breakage is easy to visually recognize. Other kinds of deterioration such as wear, corrosion, and/or distortion are not easily seen; therefore, control cables should be removed periodically for a more detailed inspection. At each annual or 100-hour inspection, all control cables must be inspected for broken wire strands. Any cable assembly that has one broken wire strand located in a critical fatigue area must be replaced." It further stated the following: "Close inspection in these critical fatigue areas, must be made by passing a cloth over the area to snag on broken wires. This will clean the cable for visual inspection, and detect broken wires if the cloth snags on the cable." It is likely that the red fibers found on the rudder cable were from a red cloth used to inspect the rudder cable during the annual inspection. It is also likely that, sometime during the flight or landing sequence, the right rudder cable separated, which subsequently restricted the pilot's ability to recover from the loss of control during landing.
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
- Flight control sys malf/fail during unknown defining event
- Other weather encounter during landing
- Loss of control on ground during landing
- Runway excursion during landing
- Collision with terrain or object (not controlled flight into terrain) during landing
The NTSB's findings
- cause Aircraft › Aircraft systems › Flight control system › Rudder control system › Failure
- Environmental issues › Conditions/weather/phenomena › Wind › Windshear › Effect on operation
- Environmental issues › Conditions/weather/phenomena › Wind › Updraft › Effect on operation
- Environmental issues › Conditions/weather/phenomena › Wind › Downdraft › Effect on operation
- Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Directional control › Attain/maintain not possible
Pilot
- Certificate: private
- Ratings: single-engine land
- Flight time: 83 hours in all; 82 in this make and model; 35 in the last 90 days; 13 in the last 30 days; 29 as pilot in command
- Medical certificate: Class 3 (with waivers/limitations)
- Seat: left
- Injury: no injuries
The aircraft
- Last inspection: annual inspection, April 14, 2017
- Maximum gross weight: 1,600 lb
- Seats: 2
- Landing gear: fixed
- Engine: Cont Motor O-200 SERIES (piston); 0 hours total
- Operator: Pocono Mountains Flying Club INC
The flight
- Departed from: MPO Mount Pocono PA at 9:30 pm
- Destination: ZER Pottsville PA
- Flight plan: none
- Runway 11, 4,599 ft by 75 ft
Weather at the time
- Light: daylight
- Visibility: 10 statute miles
- Sky: clear
- Temperature: 43°F (6°C), dew point 43°F (6°C)
- Altimeter: 30.37 inHg
- Observation at 9:58 am from KMUI, 18 miles away
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 | |||
| Passengers | 1 |
Documents from the investigation the NTSB's docket: the evidence folder behind the report
5 documents, released by the NTSB on December 11, 2017. 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.
| # | Document | What it is | |
|---|---|---|---|
| 1 | Pilot/operator Aircraft Accident Report, NTSB Form 6120.1 | PDF, 9 pages | View Download |
| 2 | Illustrated Parts Catalog - Rudder | PDF, 1 page | View Download |
| 3 | FAA Record of Converstation - Mechanic | PDF, 2 pages | View Download |
| 4 | Accident Photos | PDF, 3 pages | View Download |
| 5 | Logbook Entry | PDF, 1 page | View Download |
The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.
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.
