- Date
- September 7, 2009, 10:33 local (15:33 UTC)
- Place
- Tulsa, OK
- Injuries
- 1 uninjured
- Damage
- Substantial damage
- Phase of flight
- Takeoff
- Aircraft
- N6442YCessna T210
- Defining event
- Takeoff-rejected takeoff: Runway excursion
- Weather
- Visual (VMC) · Day
- Status
- Completed · report December 15, 2009
- Report
- Approved by Office Director
- NTSB office
- Central Region
- Parties
- FAA Oklahoma City FSDO
- FAA report
- 20090907016519A
- Case key
- 74679
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
A temporary loss of elevator pitch control for undetermined reasons.
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 private pilot was on a takeoff roll from a 4,208-foot-long paved runway. At rotation speed the yoke was unresponsive and the pilot was unable to pull the yoke back for liftoff. The pilot said that he immediately looked down and confirmed that the gust lock was not installed and aborted the takeoff. The airplane exited the runway at the departure end and the pilot performed an intentional ground loop to avoid crashing through the airport boundary fence. There was substantial damage to the airplane, but no injuries to the private pilot, who was the only occupant. The two Federal Aviation Administration inspectors who responded to the accident scene confirmed continuity of the flight controls and did not find any precrash anomalies that would have prevented normal operations.
Factual narrative
The private pilot was on takeoff roll from a 4,208 foot long paved runway. At rotation speed the yoke was unresponsive and the pilot was unable to pull the yoke back for lift off. The pilot said he immediately looked down and confirmed that the gust lock was not installed and aborted the takeoff. The airplane exited the runway at the departure end and the pilot performed an intentional ground loop to avoid crashing through the airport boundary fence. There was substantial damage to the airplane, but no injuries to the private pilot, who was the only occupant. The two FAA inspectors who responded to the accident scene confirmed continuity of the flight controls and did not find any pre-impact anomalies that would have prevented normal operations.
Aircraft
- Registration
- N6442Y
- Reported as
- Cessna T210 (N)
- Category
- Airplane
- Serial number
- 21064382
- Airframe hours
- 5,771
- Engine
- Continental TSIO-520, 300 horsepower, reciprocating
- Damage
- Substantial damage
- Flight
- Personal · Part 91
- Airworthiness certificate
- Standard, Normal
- Last inspection
- Annual · August 28, 2009
- Departed
- RVS · Tulsa, OK
- Destination
- 0R3 · Abbeville, LA
- Flight plan
- IFR
- Airport
- RVS · Richard Lloyd Jones Jr Airport, runway 01R, 4,208 × 100 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
- 65
- Injuries
- None
- Certificate
- Private
- Airplane ratings
- Single-engine land
- Instrument ratings
- Airplane
- Medical
- Class 3, With waivers/limitations
- Last flight review
- April 29, 2009
- Seat
- Left
- Flight hours
- 4,567 total · 3,377 in this make and model · 4,343 as pilot in command · 59 in the last 90 days
Weather
- Conditions
- Visual (VMC) · Day
- Wind
- 130° at 3 knots
- Visibility
- 10 statute miles
- Lowest ceiling
- None
- Temperature
- 79 °F, dew point 66 °F
- Altimeter
- 30.04 inHg
- Observed at
- RVS, 1 nm away
Docket · 1
The files NTSB released with the investigation on October 8, 2009, on NTSB’s docket system: statements, records, photos and specialists’ reports. 299 KB 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.