# NTSB WPR15LA233: Ryan Aeronautical ST3KR, N48701, Hollister, CA, August 6, 2015 - Type: NTSB accident investigation - Classification: Accident · Fatal · Limited investigation · Final report - Date: August 6, 2015, 10:30 local (17:30 UTC) - Place: Hollister, CA - Coordinates: 36.952777, -121.46389 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=36.9528&lon=-121.4639&mi=10 - Phase of flight: [Landing](https://openairdocs.org/ntsb-phases/550) (OpenAirDocs' grouping) - Defining event: [Landing-landing roll: Collision during takeoff/land](https://openairdocs.org/ntsb-events/490) - Highest injury: Fatal - Injuries: 1 fatal, 1 serious, 1 minor; on the ground: 1 fatal - Status: Completed, report September 12, 2016 - Report: Approved by Office Director - NTSB office: Western Pacific Region - Parties: Federal Aviation Administration - NTSB case key (mKey): 91720 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=WPR15LA233 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/91720/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=91720 - Page: https://openairdocs.org/ntsb/WPR15LA233 ## Probable cause The pilot's failure to observe the runway environment while operating in the traffic pattern and his subsequent failure to maintain clearance from a lawnmower on the runway during the landing roll. Contributing to the accident was the lawnmower operator's decision to remain on the runway while troubleshooting the mowing equipment without monitoring the airport's common traffic advisory frequency. ## Findings NTSB's coded findings; those marked are part of the probable cause. - [Attention/monitoring: monitoring environment](https://openairdocs.org/ntsb-findings/02021545): Personnel issues › Psychological · Pilot (probable cause); cases with it: [Ryan Aeronautical ST3KR, 1 case](https://openairdocs.org/ntsb-findings/02021545/cases.md?model=7830502), [All aircraft, 809 cases](https://openairdocs.org/ntsb-findings/02021545/cases.md) - [Attention/monitoring: monitoring communications](https://openairdocs.org/ntsb-findings/02021530): Personnel issues › Psychological · Airport personnel (probable cause); cases with it: [Ryan Aeronautical ST3KR, 1 case](https://openairdocs.org/ntsb-findings/02021530/cases.md?model=7830502), [All aircraft, 8 cases](https://openairdocs.org/ntsb-findings/02021530/cases.md) - [Physical workspace: visibility](https://openairdocs.org/ntsb-findings/03041020): Environmental issues › Task environment · Contributed to outcome; cases with it: [Ryan Aeronautical ST3KR, 1 case](https://openairdocs.org/ntsb-findings/03041020/cases.md?model=7830502), [All aircraft, 25 cases](https://openairdocs.org/ntsb-findings/03041020/cases.md) - [Info processing/decision: decision making/judgment](https://openairdocs.org/ntsb-findings/02041520): Personnel issues › Action/decision · Airport personnel; cases with it: [Ryan Aeronautical ST3KR, 1 case](https://openairdocs.org/ntsb-findings/02041520/cases.md?model=7830502), [All aircraft, 3,098 cases](https://openairdocs.org/ntsb-findings/02041520/cases.md) - [Object/animal/substance: ground vehicle](https://openairdocs.org/ntsb-findings/03022025): Environmental issues › Physical environment · Awareness of condition; cases with it: [Ryan Aeronautical ST3KR, 1 case](https://openairdocs.org/ntsb-findings/03022025/cases.md?model=7830502), [All aircraft, 132 cases](https://openairdocs.org/ntsb-findings/03022025/cases.md) ## Sequence of events The events NTSB coded, in order, by phase of flight. The defining event best describes what happened. - [Landing-landing roll: Collision with terr/obj (non-CFIT) ](https://openairdocs.org/ntsb-events/470); cases with it: [Ryan Aeronautical ST3KR, 4 cases](https://openairdocs.org/ntsb-events/470/sequence.md?model=7830502), [All aircraft, 10,189 cases](https://openairdocs.org/ntsb-events/470/sequence.md) - [Landing-landing roll: Collision during takeoff/land](https://openairdocs.org/ntsb-events/490) (defining event); cases with it: [Ryan Aeronautical ST3KR, 2 cases](https://openairdocs.org/ntsb-events/490/sequence.md?model=7830502), [All aircraft, 1,309 cases](https://openairdocs.org/ntsb-events/490/sequence.md) ## Analysis Following an uneventful flight in the tailwheel-equipped airplane, the pilot entered the airport traffic pattern for the nontowered airport, which featured a single turf runway. The pilot announced his position on the airport's common traffic advisory frequency (CTAF). The pilot continued to turn onto the base leg and then onto final, announced his position on each segment, and landed in a 3-point attitude. During the landing roll, the airplane struck a stationary, occupied lawnmower and a truck on the right side of the runway. The pilot further reported that he did not see the lawnmower while he was in the traffic pattern or during the landing sequence. The driver of the truck, who was talking to the person operating the lawnmower, reported that they were located on the right side of the runway, just beyond a turnoff to the taxiway, and were discussing an issue with the mower. The driver further reported that the lawnmower operator did have a headset connected to an aircraft transceiver; however, he was not wearing it during the conversation. It is likely that the nose-high attitude of the tailwheel-equipped airplane and the pilot's position in the rear seat reduced the pilot's forward visibility during the landing and subsequent landing roll precluded his ability to see objects directly in front of the airplane. However, the pilot would have had adequate visibility to inspect the runway for obstructions while operating in the traffic pattern. In addition, if the lawnmower operator had been using the transceiver to monitor the CTAF, it is likely that he would have heard the approaching airplane and repositioned the lawnmower off the runway before the airplane landed. ## Factual narrative On August 6, 2015, about 1030 Pacific daylight time, a tailwheel equipped Ryan Aeronautical ST3KR, N48701, was substantially damaged when it collided with an occupied riding lawn mower during landing at the Frazier Lake Airport (1C9), Hollister, California. The airplane was registered to, and operated by, the pilot under the provisions of Title 14 Code of Federal Regulations Part 91. The private pilot sustained minor injuries and the pilot rated passenger sustained serious injuries. The pilot rated occupant of the lawn mower sustained fatal injuries. Visual meteorological conditions prevailed, and no flight plan was filed for the personal flight. The local flight originated from the Reid-Hillview Airport, San Jose, California, at 1000, with 1C9 as the intended destination.In a written statement to, and a telephone conversation with the National Transportation Safety Board (NTSB) investigator-in-charge, the pilot reported that he initially transmitted his intention of landing about 8 miles from the airport on the airport's common traffic advisory frequency (CTAF). The pilot said he then entered the airport traffic pattern on a right downwind for runway 23, reported that he was on right downwind and continued to announce his position on downwind, base, and final for the runway on the CTAF. The pilot stated that he landed slightly longer than normal, and during the landing roll, the airplane struck a lawn mower. The pilot further reported that he did not see the lawnmower while he was in the traffic pattern or during the landing sequence. Examination of the airplane by a Federal Aviation Administration (FAA) aviation safety inspector revealed that the fuselage of the airplane was structurally damaged. The lawnmower, yellow in color, remained partially underneath the engine of the airplane, with the front of the lawnmower facing in the direction of travel of the airplane. In addition, the inspector reported that the airplane also struck a parked vehicle, which was white in color that was parked adjacent to the lawnmower. A witness, who was located in the run up area for runway 23, reported that he saw the lawnmower on the right side of the runway. The witness said that during his taxi to the run up area, and during his run up, he never heard any radio communication from the person on the lawnmower, however, he did hear the pilot of the accident airplane report that they were 5 miles out, followed by a report on downwind. The witness further reported that he saw the accident airplane on final approach, just crossing the runway numbers about 50 to 70 feet above ground level, and that it seemed to be fast, as if he was conducting a long landing. He then observed the airplane land in a 3-point attitude, and shortly after, impact the lawn mower. The driver of the truck who was located adjacent to the lawnmower, reported that he was having a conversation with the person who was seated on a mower about an issue he was having with it not cutting properly.He stated that they were just past the turn off to the taxiway on the right side of runway 23, and at no time heard or saw the airplane prior to the collision. He further stated that the person on the lawnmower did have a headset connected to an aircraft transceiver; however, he did not have the headset on during their conversation. 1C9 is a non-towered airport, which features a single turf runway (5/23) that is 2,500 feet in length and 100-feet wide. In addition, the airport features a water runway located adjacent to the turf runway that is 3,000 feet in length and 60-feet wide. Review of the FAA Airport Facilities Directory revealed that at the time of the accident, no remarks were present for mowing operations. In addition, at the time of the accident, no Notices to Airmen (NOTAMS) were present for mowing operations. The Ryan Aeronautical ST3KR is a two-place, tandem configured, low wing, tailwheel equipped monoplane, manufactured in 1942. The airplane is commonly flown from the aft seat, which is located just aft of the wing. Visibility from the aft seat is limited in a three-point attitude due to the nose high angle and engine. ## Aircraft - Registration: [N48701](https://openairdocs.org/aircraft/N48701), registered now, S/N 2101, built 1942 (OpenAirDocs) - Reported make and model: RYAN AERONAUTICAL ST3KR (NO SERIES) - Registry model: [Ryan Aeronautical ST3KR](https://openairdocs.org/model/ryan-aeronautical-st3kr) (registry code 7830502) (OpenAirDocs) - Registry engine: [Kinner R5 series](https://openairdocs.org/engine/kinner-r5-series) (registry code 37504, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: 2101 - Year built: 1942 - Airframe hours: 2513 - Engines: KINNER R5 SERIES 160 horsepower reciprocating - Damage: Substantial damage - Flight: Personal, Part 91 - Airworthiness certificate: Standard, Normal - Last inspection: Annual, May 15, 2014, 15 hours before - Departed: San Jose, CA - Destination: 1C9, Hollister, CA - Airport: 1C9, Frazier Lake Airpark, runway 23, 2,500 × 100 ft, grass/turf ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 75; injuries: minor; private; airplane ratings: single-engine land; medical: class 3, with waivers/limitations; last flight review July 4, 2015; seat: rear; flight hours: 2,186 total, 220 in this make and model, 2,100 as pilot in command, 10 in the last 90 days, 2 in the last 30 days, 1 in the last 24 hours ## Weather - Conditions: Visual (VMC), Day - Wind: 300° at 3 knots - Visibility: 7 statute miles - Lowest ceiling: none - Temperature: 70 °F, dew point 61 °F - Altimeter: 29.94 inHg - Observed at: KCVH, 4 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 (OpenAirDocs). - [Accident 20150806019739A](https://openairdocs.org/incident/20150806019739A), Aug 6, 2015: Ryan Aeronautical ST3KR, Hollister, CA, Substantial damage, 1 fatal. The pilot of a PT-22 (ST3KR), N48701, failed to see a tractor parked on the grass runway at Frazier lake (1C9). The aircraft subsequently impacted the tractor… ## Other investigations on N48701 (1) From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. - [NTSB OAK77DVD01](https://openairdocs.org/ntsb/OAK77DVD01), Oct 2, 1976: Ryan ST-3KR (N48701), Tracy, CA, substantial damage ## Docket (7 files) The files NTSB released with the investigation on July 12, 2016, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=91720. 2.2 MB in all. - Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (item 1, .PDF, 1.0 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40442255&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1-Master.PDF - Record of Conversation - Pilot (item 2, .PDF, 54 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40442256&FileExtension=.PDF&FileName=Record%20of%20Conversation%20-%20Pilot-Master.PDF - Record of Conversation - Witness (item 3, .PDF, 55 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40442257&FileExtension=.PDF&FileName=Record%20of%20Conversation%20-%20Witness-Master.PDF - Airport Facilities Directory Listing for the Airport on the day of the Accident (item 4, .PDF, 172 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40442258&FileExtension=.PDF&FileName=Airport%20Facilities%20Directory%20Listing%20for%20the%20Airport%20on%20the%20day%20of%20the%20Accident-Master.PDF - Airport Facilities Directory Listing with Post Accident Changes (item 5, .PDF, 91 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40442259&FileExtension=.PDF&FileName=Airport%20Facilities%20Directory%20Listing%20with%20Post%20Accident%20Changes-Master.PDF - Accident Site Photos (item 6, .PDF, 5 photos, 762 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40442260&FileExtension=.PDF&FileName=Accident%20Site%20Photos-Master.PDF - Record of Conversation - Airport Operations (item 7, .PDF, 54 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40443672&FileExtension=.PDF&FileName=Record%20of%20Conversation%20-%20Airport%20Operations-Master.PDF From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. --- OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.