# NTSB WPR14LA114: Pitts S2C, N102ZT, Roseburg, OR, January 26, 2014 - Type: NTSB accident investigation - Classification: Accident · No injuries · Limited investigation · Final report - Date: January 26, 2014, 15:30 local (23:30 UTC) - Place: Roseburg, OR - Coordinates: 43.238887, -123.355834 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=43.2389&lon=-123.3558&mi=10 - Phase of flight: [Landing](https://openairdocs.org/ntsb-phases/550) (OpenAirDocs' grouping) - Defining event: [Landing: Collision during takeoff/land](https://openairdocs.org/ntsb-events/490) - Highest injury: No injuries - Injuries: 1 uninjured - Status: Completed, report April 26, 2016 - Report: Approved by Office Director - NTSB office: Western Pacific Region - Parties: FAA FSDO - NTSB case key (mKey): 88790 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=WPR14LA114 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/88790/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=88790 - Page: https://openairdocs.org/ntsb/WPR14LA114 ## Probable cause The pilot’s loss of orientation while scanning for airport traffic during the turn from the base to final legs of the traffic pattern, which resulted in his failure to maintain clearance from a tree. ## 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: [Aviat S-2C, 2 cases](https://openairdocs.org/ntsb-findings/02021545/cases.md?model=8130001), [All aircraft, 809 cases](https://openairdocs.org/ntsb-findings/02021545/cases.md) - [Object/animal/substance: tree(s)](https://openairdocs.org/ntsb-findings/03022020): Environmental issues › Physical environment · Awareness of condition (probable cause); cases with it: [Aviat S-2C, 1 case](https://openairdocs.org/ntsb-findings/03022020/cases.md?model=8130001), [All aircraft, 933 cases](https://openairdocs.org/ntsb-findings/03022020/cases.md) - [Performance/control parameters: altitude](https://openairdocs.org/ntsb-findings/01062012): Aircraft › Aircraft oper/perf/capability · Not attained/maintained (probable cause); cases with it: [Aviat S-2C, 1 case](https://openairdocs.org/ntsb-findings/01062012/cases.md?model=8130001), [All aircraft, 1,310 cases](https://openairdocs.org/ntsb-findings/01062012/cases.md) ## Sequence of events The events NTSB coded, in order, by phase of flight. The defining event best describes what happened. - [Landing: Collision during takeoff/land](https://openairdocs.org/ntsb-events/490) (defining event); cases with it: [Aviat S-2C, 2 cases](https://openairdocs.org/ntsb-events/490/sequence.md?model=8130001), [All aircraft, 1,309 cases](https://openairdocs.org/ntsb-events/490/sequence.md) ## Analysis The commercial pilot was conducting a local personal flight. The pilot reported that he entered the traffic pattern behind a much slower airplane and observed a second (high-wing) airplane on an apparent base leg about 1 mile south of the airport. The pilot made a right 360-degree turn while on the downwind leg for spacing. After reestablishing his position on the downwind leg, he requested position reports from local area traffic. The pilot in the first airplane in the traffic pattern reported clear of the runway; the accident pilot heard no other position reports and subsequently began a normal approach to the runway. Immediately before turning to final, the pilot from an unknown airplane transmitted that his airplane was on final for the same runway. The accident pilot then rolled the airplane wings level and checked the final approach path for traffic. He observed no traffic and subsequently rolled the airplane back into a left turn to final with a shallow left forward slip. As the airplane rolled onto short final, it collided with the upper portion of a tall tree. The pilot then landed the airplane successfully. The Federal Aviation Administration Digital Airport/Facility Directory noted that the runway had a displaced threshold of 371 ft due to a tree, which was also depicted on the airport diagram. It is likely that the pilot lost his orientation with respect to the tree when he diverted his scan to look for another airplane in the traffic pattern. ## Factual narrative On January 26, 2014, about 1530 Pacific standard time, a Pitts S2C, N102ZT, collided with trees during the turn to final approach to runway 34 at Roseburg, Oregon. The pilot was operating the airplane under the provisions of 14 Code of Federal Regulations (CFR) Part 91. The commercial pilot was not injured. The airplane sustained substantial damage to the upper and lower wings. The local personal flight departed Roseburg about 1500. Visual meteorological conditions (VMC) prevailed, and no flight plan had been filed.The pilot reported that he returned from a local flight, and entered the traffic pattern behind a much slower airplane. He observed a second (high-wing) airplane crossing from west to east on an apparent base about 1 mile south of the airport. The pilot made a right 360-degree turn on downwind for spacing. He noted that hilly terrain surrounded the airport. After reestablishing his position on downwind, he requested position reports from Roseburg area traffic. The first airplane reported clear of the runway; he heard no other position reports. The pilot stated that he made a normal approach to the runway. Immediately prior to the turn to final, an unknown airplane transmitted that they were on final for runway 34. The pilot rolled wings level, and checked the final approach path for traffic. He observed none, and rolled back into a left turn to final with a shallow left forward slip. As the airplane rolled onto short final, it collided with the upper portion of a tall tree. The pilot landed the airplane successfully, and egressed from the airplane with no difficulties. The pilot reported that the tree was about 60 feet higher than a utility pole near it, and encroached into the approach flight path for landing. He also reported that the tree was not lighted. The FAA Digital Airport/Facility Directory indicated that runway 34 was 4,602 feet long and 100 feet wide. The runway surface was asphalt, and noted a displaced threshold of 371 feet for a tree, which was also depicted on the airport diagram. ## Aircraft - Registration: [N102ZT](https://openairdocs.org/deregistered/N102ZT-2018-02-02), registration cancelled 2018-02-02, S/N 6057, built 2003 (OpenAirDocs) - Reported make and model: PITTS S2C - Registry model: [Aviat S-2C](https://openairdocs.org/model/aviat-s-2c) (registry code 8130001) (OpenAirDocs) - Registry engine: [Lycoming AEIO-540 series](https://openairdocs.org/engine/lycoming-aeio-540-series) (registry code 41568, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: 6057 - Year built: 2003 - Airframe hours: 127 - Engines: Lycoming AEVI-540-O4A5 260 horsepower reciprocating - Damage: Substantial damage - Flight: Personal, Part 91 - Operator: Dave Leonard - Registered owner: BSS Arrow LLC - Airworthiness certificate: Standard, Aerobatic - Last inspection: Annual, October 23, 2013 - Departed: RBG, Roseburg, OR - Destination: RBG, Roseburg, OR - Flight plan: Company VFR - Airport: RBG, Roseburg Regional Airport, runway 34, 5,000 × 100 ft, asphalt - Equipment: Stall warning system ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 67; injuries: none; commercial, flight instructor; airplane ratings: multi-engine land, single-engine sea, single-engine land; instrument ratings: airplane; medical: class 2, with waivers/limitations; last flight review June 22, 2013; seat: rear; flight hours: 7,918 total, 328 in this make and model, 7,918 as pilot in command, 8 in the last 90 days ## Weather - Conditions: Visual (VMC), Day - Wind: calm - Visibility: 10 statute miles - Lowest ceiling: none - Temperature: 54 °F, dew point 39 °F - Altimeter: 30.05 inHg - Observed at: KRBG ## 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 20140126000919A](https://openairdocs.org/incident/20140126000919A), Jan 26, 2014: Aviat Aircraft Inc S-2C, Roseburg, OR, Substantial damage. While in his turn for final for runway 35 (while keeping visual with runway) the PIC adjusted his turn to avoid other aircraft in pattern yet failed to notice… ## Docket (1 files) The files NTSB released with the investigation on March 22, 2016, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=88790. 387 KB in all. - Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (item 1, .PDF, 387 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40437941&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1-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.