- Date
- September 10, 2003, 19:35 local (Sep 11, 2003, 00:35 UTC)
- Place
- Ardmore, OK
- Injuries
- 1 minor
- Damage
- Substantial damage
- Phase of flight
- Approach
- Aircraft
- N9651QCessna 172M
- Weather
- Visual (VMC) · Dusk
- Status
- Completed · report December 30, 2003
- Report
- Approved by Office Director
- Parties
- Federal Aviation Administration
- FAA report
- 20030910023529A
- Case key
- 57908
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 failure of the pilot to adequately compensate for existing wind conditions. A contributing factor was the gusty crosswind conditions from the east.
Sequence of events
NTSB’s coding before 2008: each occurrence and phase of flight, and the causes and factors under it. The codes are defined in NTSB’s coding manual.
Analysis
The aircraft collided with trees while in the airport traffic pattern. According to the pilot, he encountered a downdraft while turning left base for a landing to the runway. Runway 17 is 5,000 feet long and 75 feet wide. Wind was reported by the weather observation facility at 1F0 to be from the southeast at 9 to 11 knots, with gusts to 16 knots. Official sunset was calculated by the Astronomical Applications Department of the U.S. Naval Observatory to be 1943.
Factual narrative
On September 10, 2003, about 1935 central daylight time, a Cessna 172M single-engine airplane, N9651Q, was substantially damaged when it impacted the ground following a loss of control while landing at Ardmore Downtown Executive Airport (1F0) near Ardmore, Oklahoma. The private pilot, sole occupant of the airplane, received minor injuries. The airplane was registered to and operated by Litchfield Flying Ltd., of Ardmore, Oklahoma. Visual meteorological conditions prevailed, and a flight plan was not filed for the 14 Code of Federal Regulations Part 91 personal flight, which departed 1F0 approximately 1835.
In a written statement to the FAA, the 43-hour pilot, who was a visiting German citizen, stated that the airplane "experienced a sudden downdraft" while turning left base for landing to runway 17, and "the next thing I remember, I was sitting in a tree."
Examination of the airplane by an FAA inspector, who responded to the accident site, revealed that the airplane collided with a tree in a residential yard before impacting the ground. The airplane incurred major structural damage to the fuselage, wings, and flight controls. The accident site was located west of the centerline of runway 17, abeam the airport boundary.
Runway 17 is 5,000 feet long and 75 feet wide. Wind was reported by the weather observation facility at 1F0 to be from the southeast at 9 to 11 knots, with gusts to 16 knots. Official sunset was calculated by the Astronomical Applications Department of the U.S. Naval Observatory to be 1943.
Aircraft
- Registration
- N9651Q
- Reported as
- Cessna 172M
- Category
- Airplane
- Serial number
- 172-65735
- Airframe hours
- 8,562.5
- Engine
- Lycoming O-320-E2D, 150 horsepower, reciprocating
- Damage
- Substantial damage
- Flight
- Personal · Part 91
- Registered owner
- Joe T. Litchfield
- Airworthiness certificate
- Standard, Normal
- Last inspection
- Annual · April 30, 2003 · 41.5 hours before
- Departed
- 1F0 · Ardmore
- Airport
- 1FO · Ardmore Downtown Executive, runway 17, 5,000 × 75 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
- 32
- Injuries
- Minor
- Certificate
- Private
- Airplane ratings
- Single-engine land
- Medical
- Class 3
- Last flight review
- April 11, 2003
- Seat
- Left
- Flight hours
- 43 total · 42 in this make and model
Weather
- Conditions
- Visual (VMC) · Dusk
- Wind
- 140° at 9 knots, gusting 16
- Visibility
- 10 statute miles
- Lowest ceiling
- None
- Temperature
- 90 °F, dew point 70 °F
- Altimeter
- 29.88 inHg
- Observed at
- ADM, 15 nm away
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 N9651Q · 1
Matched to the same aircraft by N-number and date.