# NTSB WPR11TA083: Quest Kodiak 100, N702FW, Reedsport, OR, December 31, 2010 - Type: NTSB accident investigation - Classification: Accident · No injuries · Final report - Date: December 31, 2010, 10:55 local (18:55 UTC) - Place: Reedsport, OR - Coordinates: 43.750556, -124.02639 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=43.7506&lon=-124.0264&mi=10 - Phase of flight: [Maneuvering](https://openairdocs.org/ntsb-phases/450) (OpenAirDocs' grouping) - Defining event: [Maneuvering: Controlled flight into terr/obj (CFIT)](https://openairdocs.org/ntsb-events/120) - Highest injury: No injuries - Injuries: 3 uninjured - Status: Completed, report November 29, 2011 - Report: Approved by Office Director - NTSB office: Western Pacific Region - Parties: Portland FAA FSDO - NTSB case key (mKey): 78085 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=WPR11TA083 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/78085/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=78085 - Page: https://openairdocs.org/ntsb/WPR11TA083 ## Probable cause The pilot's failure to maintain clearance from power lines during a low-level aerial observation flight. Contributing to the accident was pilot's failure to review a route hazards map prior to initiating the flight. ## 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: [All aircraft, 809 cases](https://openairdocs.org/ntsb-findings/02021545/cases.md) - [Planning/preparation: flight planning/navigation](https://openairdocs.org/ntsb-findings/02061025): Personnel issues › Task performance · Pilot (probable cause); cases with it: [All aircraft, 179 cases](https://openairdocs.org/ntsb-findings/02061025/cases.md) - [Object/animal/substance: wire](https://openairdocs.org/ntsb-findings/03022032): Environmental issues › Physical environment · Response/compensation (probable cause); cases with it: [All aircraft, 588 cases](https://openairdocs.org/ntsb-findings/03022032/cases.md) - [Knowledge: knowledge of geographic area](https://openairdocs.org/ntsb-findings/02032030): Personnel issues › Experience/knowledge · Pilot; cases with it: [All aircraft, 24 cases](https://openairdocs.org/ntsb-findings/02032030/cases.md) ## Sequence of events The events NTSB coded, in order, by phase of flight. The defining event best describes what happened. - [Maneuvering: Low altitude operation/event](https://openairdocs.org/ntsb-events/220); cases with it: [All aircraft, 780 cases](https://openairdocs.org/ntsb-events/220/sequence.md) - [Maneuvering: Controlled flight into terr/obj (CFIT)](https://openairdocs.org/ntsb-events/120) (defining event); cases with it: [All aircraft, 1,074 cases](https://openairdocs.org/ntsb-events/120/sequence.md) ## Analysis While flying a low-level waterfowl aerial observation route, the pilot flew into power lines that were strung across a river. While both the pilot and a passenger saw the power lines just before impact, it was too late to take action. Because the pilot normally flew in a different region, and was on temporary assignment in a geographical area that he was not familiar with, he was unaware of the specific hazards along the subject route. He also did not possess a copy of the local area hazards map, although one had been sent to him as part of a multi-attachment email. During a reconnaissance flight prior to the accident, the pilot identified several hazards, but not the wires that he ultimately impacted. ## Factual narrative On December 31, 2010, about 1055 Pacific standard time, a Quest Kodiak 100, N702FW, impacted a set of power lines strung across the Smith River about five miles northeast of Reedsport, Oregon. The commercial pilot and his two passengers were not injured, but the airplane, which was owned and operated by the United States Department of Interior, sustained substantial damage. The Public Use migratory waterfowl aerial observation flight, which departed North Bend Regional Airport, North Bend, Oregon, about 1000, had a planned destination of Astoria, Oregon. At the time of the accident, the plane was being operated in visual meteorological conditions. The pilot filed and activated a visual flight rules (VFR) flight plan. According to the pilot, prior to making his low-level observation flight up the Smith River, he first made a high reconnaissance flight along the route at 500 feet above ground level (AGL) in order to look for any possible obstructions. During the reconnaissance flight, the crew identified several hazards, but not the wires that were ultimately impacted. He then began his observation flight, maintaining an altitude between 120 and 150 feet AGL. When he was about five miles northeast of Reedsport, the airplane impacted the power lines. The pilot further stated that although he saw the power line immediately prior to the impact, he did not have time enough to take evasive action that would have avoided the wires. After the impact, the pilot checked the plane's controllability, and then made the decision to return to North Bend Regional Airport for landing. The impact with the power line resulted in a rip of the skin and deformation of one aileron, and several chunks of metal being torn from the leading edge of the propeller. The investigation determined that the mission was flown by a pilot/biologist from the U.S. Fish and Wildlife Service (FWS) Region 7 (Alaska), a biologist/observer from FWS Region 9 (Minnesota), and a retired FWS biologist/observer (contractor) from Alaska. The biologist/observer from region 9 was the only occupant who had flown a Migratory Waterfowl Survey (MWS) in the Pacific Region before. The pilot and the Region 7 biologist/observer were unfamiliar with both the survey track lines and the associated hazards. It was also determined that the pilot did not possess a hazards map for the low-level survey route that he flew, although such a map, which depicted the wires that were struck, existed, and had been sent to him as part of a multi-attachment email. ## Aircraft - Registration: N702FW (not matched to a registry record) - Reported make and model: Quest Kodiak 100 - Category: Airplane - Serial number: 100-0035 - Airframe hours: 38 - Engines: Pratt & Whitney PT6-34 750 horsepower turbo prop - Damage: Substantial damage - Flight: Aerial observation, Public use - Operator: United States Department Of Interior - Registered owner: United States Department Of Interior - Airworthiness certificate: Standard, Normal - Last inspection: Annual, January 27, 2010, 38 hours before - Departed: KOTH, North Bend, OR - Destination: KAST, Astoria, OR - Flight plan: VFR ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 50; injuries: none; commercial, flight instructor; airplane ratings: multi-engine land, single-engine land, single-engine sea; instrument ratings: airplane; medical: class 2, with waivers/limitations; last flight review September 3, 2010; seat: left; flight hours: 13,000 total, 50 in this make and model, 12,000 as pilot in command, 75 in the last 90 days, 25 in the last 30 days, 4 in the last 24 hours ## Weather - Conditions: Visual (VMC), Day - Wind: 90° at 10 knots - Visibility: 10 statute miles - Lowest ceiling: none - Temperature: 43 °F - Altimeter: 29.95 inHg ## 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 20101231055959A](https://openairdocs.org/incident/20101231055959A), Dec 31, 2010: Quest Aircraft Company LLC KODIAK 100, Reedsport, OR, Substantial damage. On December 31, 2010, about 1055 pacific standard time, a Quest kodiak 100, N702FW, impacted a power line strung across the smith river about five miles… ## Docket (2 files) The files NTSB released with the investigation on October 21, 2011, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=78085. 232 KB in all. - Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (item 1, .PDF, 149 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40354900&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1-Redacted.PDF - Record of Conversation (item 2, .PDF, 83 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40354872&FileExtension=.PDF&FileName=Record%20of%20Conversation-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.