# NTSB GAA17CA185: Pipistrel Doo Ajdovscina Virus, N345M, Okmulgee, OK, March 11, 2017 - Type: NTSB accident investigation - Classification: Accident · No injuries · Data collection · Final report - Date: March 11, 2017, 08:10 local (14:10 UTC) - Place: Okmulgee, OK - Coordinates: 35.665, -95.946113 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=35.6650&lon=-95.9461&mi=10 - Phase of flight: [Landing](https://openairdocs.org/ntsb-phases/550) (OpenAirDocs' grouping) - Defining event: [Landing-landing roll: Miscellaneous/other](https://openairdocs.org/ntsb-events/900) - Highest injury: No injuries - Injuries: 2 uninjured - Status: Completed, report September 22, 2017 - Report: Approved by Office Director - NTSB office: General Aviation Accidents - Parties: FAA - NTSB case key (mKey): 94861 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=GAA17CA185 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/94861/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=94861 - Page: https://openairdocs.org/ntsb/GAA17CA185 ## Probable cause The pilot’s failure to review the Federal Aviation Administration chart supplement before landing, which resulted in his landing on a closed runway and collision with a fence. Contributing to the accident was the airport’s failure to adequately mark the physical surface of the runway to indicate that it was permanently closed. ## Findings NTSB's coded findings; those marked are part of the probable cause. - [Planning/preparation](https://openairdocs.org/ntsb-findings/02061000): Personnel issues › Task performance · Pilot (probable cause); cases with it: [Pipistrel Doo Ajdovscina VIRUS SW, 1 case](https://openairdocs.org/ntsb-findings/02061000/cases.md?model=056321O), [All aircraft, 113 cases](https://openairdocs.org/ntsb-findings/02061000/cases.md) - [Object/animal/substance: fence/fence post](https://openairdocs.org/ntsb-findings/03022047): Environmental issues › Physical environment · Effect on equipment; cases with it: [Pipistrel Doo Ajdovscina VIRUS SW, 1 case](https://openairdocs.org/ntsb-findings/03022047/cases.md?model=056321O), [All aircraft, 313 cases](https://openairdocs.org/ntsb-findings/03022047/cases.md) - [Airport facilities/design: runway markings/signage](https://openairdocs.org/ntsb-findings/03017030): Environmental issues › Operating environment · Effect on operation; cases with it: [Pipistrel Doo Ajdovscina VIRUS SW, 1 case](https://openairdocs.org/ntsb-findings/03017030/cases.md?model=056321O), [All aircraft, 8 cases](https://openairdocs.org/ntsb-findings/03017030/cases.md) ## Sequence of events The events NTSB coded, in order, by phase of flight. The defining event best describes what happened. - [Prior to flight: Preflight or dispatch event](https://openairdocs.org/ntsb-events/030); cases with it: [Pipistrel Doo Ajdovscina VIRUS SW, 1 case](https://openairdocs.org/ntsb-events/030/sequence.md?model=056321O), [All aircraft, 355 cases](https://openairdocs.org/ntsb-events/030/sequence.md) - [Landing-landing roll: Miscellaneous/other](https://openairdocs.org/ntsb-events/900) (defining event); cases with it: [Pipistrel Doo Ajdovscina VIRUS SW, 1 case](https://openairdocs.org/ntsb-events/900/sequence.md?model=056321O), [All aircraft, 1,556 cases](https://openairdocs.org/ntsb-events/900/sequence.md) ## Analysis The pilot reported that he entered the traffic pattern for runway 4 about 800 ft above the ground. He added that, after touchdown, he did not see the fence that ran across the runway until the airplane was about 300 ft from it. Subsequently, the airplane impacted the fence. The airplane sustained substantial damage to the fuselage and right wing. A review of the airport's Federal Aviation Administration (FAA) chart supplement (02 MAR 2017 to 27 APR 2017) revealed that the runway the pilot landed on was depicted in the airport sketch with two "X" marks, which indicated that the runway was closed. A review of the visual flight rules sectional chart in publication at the time of the accident revealed that the surface the pilot landed was depicted along with the other runway surface at the airport. The FAA Pilot's Handbook of Aeronautical Knowledge stated, in part: Marking and Lighting of Permanently Closed Runways and Taxiways For runways and taxiways that are permanently closed, the lighting circuits are disconnected. The runway threshold, runway designation, and touchdown markings are obliterated and yellow "Xs" are placed at each end of the runway and at 1,000-foot intervals. A review of photographs of the "X" markings on the surface the pilot landed on showed that only fragments of faded yellow paint were visible and that what was visible did not resemble an "X." Code of Federal Regulations Section 91.103, "Preflight Action," stated, in part: Each pilot in command shall, before beginning a flight, become familiar with all available information concerning that flight. This information must include— (a) For a flight under IFR [instrument flight rules] or a flight not in the vicinity of an airport, weather reports and forecasts, fuel requirements, alternatives available if the planned flight cannot be completed, and any known traffic delays of which the pilot in command has been advised by ATC [air traffic control]; (b) For any flight, runway lengths at airports of intended use, and the…takeoff and landing distance information. The pilot did not report that he consulted the FAA chart supplement before landing, which depicted the runway closed. ## Factual narrative The pilot reported that, he entered the traffic pattern for runway 4, about 800 ft above the ground. He added that, after touch down he did not see the fence that ran across the runway until the airplane was about 300 ft from it. Subsequently the airplane impacted the fence. The airplane sustained substantial damage to the fuselage and right wing. A review of the Okmulgee Regional Airport Federal Aviation Administration (FAA) chart supplement (02 MAR 2017 to 27 APR 2017) revealed that the runway the pilot landed on was depicted in the airport sketch with two "X" marks, which indicated the runway was closed. A review of the visual flight rules sectional chart in publication at the time of the accident revealed that the surface the pilot landed was depicted, along with the other runway surface at the airport. The FAA Pilot's Handbook of Aeronautical Knowledge stated in part: Marking and Lighting of Permanently Closed Runways and Taxiways For runways and taxiways that are permanently closed, the lighting circuits are disconnected. The runway threshold, runway designation, and touchdown markings are obliterated and yellow "Xs" are placed at each end of the runway and at 1,000-foot intervals. A review of photographs of the "X" markings on the surface the pilot landed on, showed that only fragments of faded yellow paint were visible, and what was visible did not resemble an "X". The code of federal regulations within part §91.103 titled "Preflight Action" stated in part: Each pilot in command shall, before beginning a flight, become familiar with all available information concerning that flight. This information must include— (a) For a flight under IFR or a flight not in the vicinity of an airport, weather reports and forecasts, fuel requirements, alternatives available if the planned flight cannot be completed, and any known traffic delays of which the pilot in command has been advised by ATC; (b) For any flight, runway lengths at airports of intended use, and the following takeoff and landing distance information: The pilot did not report that he consulted the FAA chart supplement prior to landing, which depicted the runway closed. ## Aircraft - Registration: [N345M](https://openairdocs.org/aircraft/N345M), registered now, S/N 621 SW 100, built 2014 (OpenAirDocs) - Reported make and model: PIPISTREL DOO AJDOVSCINA VIRUS (SW) - Registry model: [Pipistrel Doo Ajdovscina VIRUS SW](https://openairdocs.org/model/pipistrel-doo-ajdovscina-virus-sw) (registry code 056321O) (OpenAirDocs) - Registry engine: [Rotax 912ULS2](https://openairdocs.org/engine/rotax-912uls2) (registry code 55599, 4 cycle) (OpenAirDocs) - Category: Glider - Serial number: 621 SW 100 - Year built: 2014 - Airframe hours: 103.5 - Engines: Rotax 912 ULS 100 horsepower reciprocating - Damage: Substantial damage - Flight: Personal, Part 91 - Airworthiness certificate: Special, Experimental (Special); Special, Special flight (Special) - Last inspection: Condition, July 12, 2016 - Departed: 43OK, WELLSTON, OK - Destination: OKM, Okmulgee, OK - Airport: OKM, Okmulgee Rgnl - Equipment: Electronic primary flight display, Electronic multifunction display, Electronic flight bag or handheld device, Data recorder, ADS-B, Angle of attack indicator, Onboard weather, Satellite tracking device, Airframe parachute, Stall warning system ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 74; injuries: none; flight instructor, commercial; airplane ratings: multi-engine land, single-engine land; medical: class 2, with waivers/limitations; last flight review August 5, 2016; seat: left; restraint: 3-point; flight hours: 8,500 total, 50 in this make and model, 8,400 as pilot in command, 50 in the last 90 days ## Weather - Conditions: Visual (VMC), Day - Wind: 40° at 11 knots, gusting 15 - Visibility: 10 statute miles - Lowest ceiling: 3,500 ft overcast - Temperature: 43 °F, dew point 41 °F - Altimeter: 30.22 inHg - Observed at: KOKM ## 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 20170311001239A](https://openairdocs.org/incident/20170311001239A), Mar 11, 2017: Pipistrel Doo Ajdovscina VIRUS SW, Okmulgee, OK, Substantial damage. On March 11, 2017, at about 0810 central standard time, a glider-Pipistrel Doo Ajdovscina, Virus Sw, N345M, registered to a private owner, operating as a 14… ## Docket (3 files) The files NTSB released with the investigation on August 22, 2017, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=94861. 4.2 MB in all. - Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (item 1, .PDF, 3.5 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40455573&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1-Master.PDF - Okmulgee RGNL Chart Supplement (item 2, .PDF, 214 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40455574&FileExtension=.PDF&FileName=Okmulgee%20RGNL%20Chart%20Supplement-Master.PDF - Accident Photo (item 3, .PDF, 435 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40455575&FileExtension=.PDF&FileName=Accident%20Photo-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.