- Date
- May 31, 2003, 09:30 local (15:30 UTC)
- Place
- Dillon, MT
- Injuries
- 1 uninjured
- Damage
- Substantial damage
- Phase of flight
- Takeoff
- Aircraft
- N4424UCessna 150
- Weather
- Visual (VMC) · Day
- Status
- Completed · report November 25, 2003
- Report
- Approved by Office Director
- Parties
- Helena FSDO
- FAA report
- 20030531011319A
- Case key
- 57092
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 failure to maintain directional control during the takeoff roll, and his inadequate remedial actions during his attempt to realign the aircraft with the runway. Factors include a crosswind, and the pilot's lack of experience in tailwheel-equipped aircraft.
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
During the last part of the takeoff roll, the aircraft encountered a crosswind and was pushed toward the side of the runway. Although he attempted to realign the aircraft with the runway, the pilot was unable to do so, and the aircraft departed the side of the runway surface. After departing the runway, the aircraft collided with a nearby fence. The pilot stated that he had been flying nose gear aircraft for 34 years, and simply needed more tailwheel experience, of which he had only 20 hours, before attempting a takeoff in crosswind conditions. He further stated that he did not believe there was anything wrong with the aircraft's flight controls or tailwheel steering mechanism.
Factual narrative
On May 31, 2003, approximately 0930 mountain daylight time, a tailwheel-equipped Cessna 150, N4424U, collided with a fence during the takeoff roll at a private airstrip near Dillon, Montana. The private pilot, who was the sole occupant, was not injured, but the aircraft, which is owned and operated by the pilot, sustained substantial damage. The intended 14 CFR Part 91 personal pleasure flight was planned to terminate at Salmon, Idaho. At the time of the accident, the aircraft was being operated in visual meteorological conditions. No flight plan had been filed. There was no report of an ELT activation.
According to the pilot, during the last part of the takeoff roll, the aircraft encountered a crosswind and was pushed toward the side of the runway. Although he attempted to realign the aircraft with the runway, the pilot was unable to do so, and the aircraft departed the side of the runway surface. After departing the runway, the aircraft collided with a nearby fence. The pilot stated that he had been flying nose gear aircraft for 34 years, and simply needed more tailwheel experience, of which he had only 20 hours, before attempting a takeoff in crosswind conditions. He further stated that he did not believe there was anything wrong with the aircraft's flight controls or tailwheel steering mechanism.
Aircraft
- Registration
- N4424U
- Reported as
- Cessna 150
- Category
- Airplane
- Serial number
- 15060424
- Engine
- Lycoming O-320-E2D, 150 horsepower, reciprocating
- Damage
- Substantial damage
- Flight
- Personal · Part 91
- Registered owner
- Richard G. McAfee
- Airworthiness certificate
- Standard, Normal
- Last inspection
- Annual · October 1, 2002 · 20 hours before
- Departed
- Dillon, MT
- Destination
- SMN · Salmon, ID
- Airport
- McAfee Airstrip
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
- 75
- Injuries
- None
- Certificate
- Private
- Airplane ratings
- Single-engine land
- Medical
- Class 3, Valid Medical--w/ waivers/lim
- Last flight review
- May 25, 2001
- Seat
- Left
- Flight hours
- 1,500 total · 20 in this make and model · 20 in the last 90 days
Weather
- Conditions
- Visual (VMC) · Day
- Wind
- Variable at 10 knots
- Visibility
- 10 statute miles
- Lowest ceiling
- None
- Temperature
- 75 °F
FAA reports on this event · 1
The FAA’s own accident and incident reports, matched to the aircraft by N-number and date.