- Date
- August 24, 2013, 10:00 local (14:00 UTC)
- Place
- Mitchellville, MD
- Injuries
- 4 uninjured
- Damage
- Substantial damage
- Phase of flight
- Landing
- Aircraft
- N98923Cessna 172P
- Defining event
- Landing-flare/touchdown: Loss of control on ground
- Weather
- Visual (VMC) · Day
- Status
- Completed · report October 21, 2013
- Report
- Approved by Office Director
- NTSB office
- Eastern Region Aviation
- Parties
- FAA/FSDO
- FAA report
- 20130824016549A
- Case key
- 87863
From the NTSB’s public API. By law, NTSB reports can’t be used as evidence in lawsuits over the accident.
On this page
Probable cause
The pilot’s decision to depart with a known deficiency following a hard landing. Contributing to the accident was an anomaly of the airplane’s nosewheel steering that could not be replicated during post-accident examination.
Findings · 2
NTSB’s coded findings. Those marked are part of the probable cause; the rest are factors or other findings. Under each, the cases with the same finding.
Sequence of events
The events NTSB coded, in order, by phase of flight. The defining event is the one that best describes the accident. Under each, the cases with the same event anywhere in their sequence.
Analysis
The pilot reported that while taxiing for takeoff for a local flight with passengers, the right rudder felt “stiff.” Once in the air, the rudder operated normally; however, the pilot’s first landing was “hard.” After picking up a second set of passengers, the pilot noticed that while taxiing back to the runway, the right rudder felt even more stiff. At one point during the taxi, the pilot “stomped” on the rudder to steer the airplane right, but did not think much of the anomaly, as the airplane seemed to move normally after applying additional engine power. During the subsequent takeoff, the pilot noticed that the right rudder pedal continued to feel stiffer than it had during the previous takeoff. During the second landing, the airplane veered immediately left upon touchdown and departed the runway. The pilot attempted to correct the airplane’s course, but the right rudder pedal was unresponsive. The pilot then attempted to abort the landing, but once in the air, he realized the airplane would not be able to climb above approaching trees and decided to land the airplane in a farm field. During the landing the nose landing gear collapsed and the airplane nosed over, resulting in substantial damage. A Federal Aviation Administration inspector examined the airframe and flight controls following the accident and confirmed that the rudder was free to move, but that the nose steering system of the airplane had been compromised during the accident and its pre-impact functionality could not be determined. When asked how the accident could have been prevented the pilot stated, “After a hard land[ing] have the plane inspected – Don’t takeoff even if it seems normal.”
Factual narrative
The pilot reported that while taxiing for takeoff for a local flight with passengers, the right rudder felt “stiff.” Once in the air, the rudder operated normally; however, the pilot’s first landing was “hard.” After picking up a second set of passengers, the pilot noticed that while taxiing back to the runway, the right rudder felt even more stiff. At one point during the taxi, the pilot “stomped” on the rudder to steer the airplane right, but did not think much of the anomaly, as the airplane seemed to move normally after applying additional engine power. During the subsequent takeoff, the pilot noticed that the right rudder pedal continued to feel stiffer than it had during the previous takeoff. During the second landing, the airplane veered immediately left upon touchdown and departed the runway. The pilot attempted to correct the airplane’s course, but the right rudder pedal was unresponsive. The pilot then attempted to abort the landing, but once in the air, he realized the airplane would not be able to climb above approaching trees and decided to land the airplane in a farm field. During the landing the nose landing gear collapsed and the airplane nosed over, resulting in substantial damage. A Federal Aviation Administration inspector examined the airframe and flight controls following the accident and confirmed that the rudder was free to move, but that the nose steering system of the airplane had been compromised during the accident and its pre-impact functionality could not be determined. When asked how the accident could have been prevented the pilot stated, “After a hard land[ing] have the plane inspected – Don’t takeoff even if it seems normal.”
Aircraft
- Registration
- N98923
- Reported as
- Cessna 172P
- Category
- Airplane
- Serial number
- 17276381
- Airframe hours
- 12,252
- Engine
- Lycoming O-320-D2J, 160 horsepower, reciprocating
- Damage
- Substantial damage
- Flight
- Personal · Part 91
- Operator
- Freeway Airport Inc
- Registered owner
- Freeway Airport Inc
- Airworthiness certificate
- Standard, Normal; Standard, Utility
- Last inspection
- 100 hour · June 26, 2013
- Departed
- W00 · Mitchellville, MD
- Destination
- W00 · Mitchellville, MD
- Flight plan
- VFR
- Airport
- W00 · Freeway Airport, runway 36, 2,420 × 40 ft, asphalt
Matched to the registry by N-number and the event date; the registry’s history has gaps, so older matches can be wrong. Compare the reported make and model.
Flight crew
As NTSB recorded them. NTSB leaves out names.
- Role
- Pilot
- Age
- 43
- Injuries
- None
- Certificate
- Private
- Airplane ratings
- Single-engine land
- Medical
- Class 3, Without waivers/limitations
- Last flight review
- June 14, 2013
- Seat
- Left
- Flight hours
- 80 total · 80 in this make and model · 17 as pilot in command · 3 in the last 90 days · 3 in the last 30 days · 1 in the last 24 hours
Weather
- Conditions
- Visual (VMC) · Day
- Wind
- 40° at 4 knots
- Visibility
- 10 statute miles
- Lowest ceiling
- None
- Temperature
- 73 °F, dew point 61 °F
- Altimeter
- 30.27 inHg
- Observed at
- CGS, 7 nm away
Docket · 4
The files NTSB released with the investigation on September 25, 2013, on NTSB’s docket system: statements, records, photos and specialists’ reports. 4.5 MB in all.
FAA reports on this event · 1
The FAA’s own accident and incident reports, matched to the aircraft by N-number and date.
Other investigations on N98923 · 2
Matched to the same aircraft by N-number and date.