- Date
- July 31, 2010, 16:50 local (23:50 UTC)
- Place
- Santa Rosa, CA
- Injuries
- 2 uninjured
- Phase of flight
- Taxi
- Defining events
- Taxi: Ground collisionStanding-engine(s) operating: Miscellaneous/other
- Weather
- Visual (VMC) · Day
- Status
- Completed · report January 7, 2011
- Report
- Approved by Office Director
- NTSB office
- Western Pacific Region
- Parties
- Federal Aviation Administration
- FAA report
- 20100731053502A
- Case key
- 76843
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 of another airplane to maintain clearance while taxiing.
The failure of the pilot to maintain clearance from another airplane while taxiing.
Findings · 3
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.
N46590 · Boeing PT-13B
N20230 · Cessna 172M
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.
N46590 · Boeing PT-13B
N20230 · Cessna 172M
Analysis
The pilot of a Boeing PT-13B Stearman reported that after conducting maintenance on his airplane, he taxied to the run-up area to conduct an engine run-up. With the airplane being a tailwheel-type configuration, he made continuous S-turns to ensure visibility ahead of his position. While approaching the run-up area, during a turn to the right, he observed an airplane on the runway. He reported that he was “clear” in front of the airplane and he continued his S-turn to the left. During the turn, the Stearman collided with a Cessna 172M. The pilot of the Stearman stated that he did not see the Cessna prior to that final turn when he saw its empennage. The pilot of the Cessna 172M stated that he was stopped in the run-up area conducting a run-up when he looked to the left and observed the Stearman adjacent to the end of the Cessna’s left wing. He stated that the Stearman taxied forward and the propeller struck the left wing, resulting in substantial damage. Neither pilot reported mechanical failures or malfunctions with their respective airplane’s airframe or engine prior to the accident.
The pilot of a Boeing PT-13B Stearman reported that after conducting maintenance on his airplane, he taxied to the run-up area to conduct an engine run-up. With the airplane being a tailwheel-type configuration, he made continuous S-turns to ensure visibility ahead of his position. While approaching the run-up area, during a turn to the right, he observed an airplane on the runway. He reported that he was “clear” in front of the airplane and he continued his S-turn to the left. During the turn, the Stearman collided with a Cessna 172M. The pilot of the Stearman stated that he did not see the Cessna prior to that final turn when he saw its empennage. The pilot of the Cessna 172M stated that he was stopped in the run-up area conducting a run-up when he looked to the left and observed the Stearman adjacent to the end of the Cessna’s left wing. He stated that the Stearman taxied forward and the propeller struck the left wing, resulting in substantial damage. Neither pilot reported mechanical failures or malfunctions with their respective airplane’s airframe or engine prior to the accident.
Factual narrative
The pilot of a Boeing PT-13B Stearman reported that after conducting maintenance on his airplane, he taxied to the run-up area to conduct an engine run-up. With the airplane being a tailwheel typed configuration, he made continuous S-turns to ensure visibility ahead of his position. While approaching the run-up area, during a turn to the right he observed an airplane on the runway. He reported that it was “clear” in front of the airplane and he continued his S-turn to the left. During the turn, the Stearman collided with a Cessna 172M. The pilot of the Stearman stated that he did not see the Cessna prior to that final turn when he saw its empennage. The pilot of the Cessna 172M stated that he was stopped in the run-up area conducting a run-up when he looked to the left and observed the Stearman adjacent to the end of the Cessna’s left wing. He stated that the Stearman taxied forward and the propeller struck the left wing resulting in substantial damage. Neither pilot reported mechanical failures or malfunctions with their respective airplane’s airframe or engine prior to the accident.
The pilot of a Boeing PT-13B Stearman reported that after conducting maintenance on his airplane, he taxied to the run-up area to conduct an engine run-up. With the airplane being a tailwheel typed configuration, he made continuous S-turns to ensure visibility ahead of his position. While approaching the run-up area, during a turn to the right he observed an airplane on the runway. He reported that it was “clear” in front of the airplane and he continued his S-turn to the left. During the turn, the Stearman collided with a Cessna 172M. The pilot of the Stearman stated that he did not see the Cessna prior to that final turn when he saw its empennage. The pilot of the Cessna 172M stated that he was stopped in the run-up area conducting a run-up when he looked to the left and observed the Stearman adjacent to the end of the Cessna’s left wing. He stated that the Stearman taxied forward and the propeller struck the left wing resulting in substantial damage. Neither pilot reported mechanical failures or malfunctions with their respective airplane’s airframe or engine prior to the accident.
Aircraft · 2
- Registration
- N46590
- Reported as
- Boeing PT-13B
- Category
- Airplane
- Serial number
- 75-297
- Airframe hours
- 5,476
- Engine
- Lycoming R680, 215 horsepower, reciprocating
- Damage
- Minor damage
- Flight
- Personal · Part 91
- Airworthiness certificate
- Standard, Aerobatic
- Last inspection
- Annual · July 6, 2010 · 5 hours before
- Departed
- KSTS · Santa Rosa, CA
- Destination
- KSTS · Santa Rosa, CA
- Flight plan
- Unknown
- Airport
- KSTS · Charles M Schulz-Sonoma County, runway 14, 5,119 × 150 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.
- Registration
- N20230
- Reported as
- Cessna 172M
- Category
- Airplane
- Serial number
- 17261115
- Airframe hours
- 9,654
- Engine
- Lycoming O-320 SERIES, 180 horsepower, reciprocating
- Damage
- Substantial damage
- Flight
- Personal · Part 91
- Operator
- North Coast Air, Inc.
- Registered owner
- Cessna 20230 LLC
- Airworthiness certificate
- Standard, Normal
- Last inspection
- 100 hour · April 30, 2010 · 87 hours before
- Departed
- KSTS · Santa Rosa, CA
- Destination
- KSTS · Santa Rosa, CA
- Airport
- KSTS · Charles M Schulz-Sonoma County, runway 14, 5,119 × 150 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 · 2
As NTSB recorded them. NTSB leaves out names.
- Role
- Pilot, aircraft N46590
- Age
- 57
- Injuries
- None
- Certificates
- Commercial, Flight instructor, Airline transport
- Airplane ratings
- Single-engine land, Multi-engine land
- Instrument ratings
- Airplane
- Medical
- Class 2, With waivers/limitations
- Last flight review
- April 8, 2009
- Seat
- Rear
- Flight hours
- 8,000 total · 100 in this make and model · 8,000 as pilot in command
- Role
- Student pilot, aircraft N20230
- Age
- 59
- Injuries
- None
- Certificate
- Student
- Medical
- Class 3, With waivers/limitations
- Seat
- Left
- Flight hours
- 262 total · 260 in this make and model · 35 as pilot in command · 85 in the last 90 days · 11 in the last 30 days · 0 in the last 24 hours
Weather
- Conditions
- Visual (VMC) · Day
- Wind
- 190° at 8 knots
- Visibility
- 10 statute miles
- Lowest ceiling
- None
- Temperature
- 79 °F, dew point 54 °F
- Altimeter
- 29.86 inHg
- Observed at
- KSTS
Docket · 2
The files NTSB released with the investigation on September 28, 2010, on NTSB’s docket system: statements, records, photos and specialists’ reports. 1.2 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.