GAA17CA185

NTSB accident investigation · Pipistrel Doo Ajdovscina Virus · Okmulgee, OK · March 11, 2017

Accident · No injuriesData collectionFinal report
Date
March 11, 2017, 08:10 local (14:10 UTC)
Place
Okmulgee, OK
Injuries
2 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N345MPipistrel Doo Ajdovscina Virus
Defining event
Landing-landing roll: Miscellaneous/other
Weather
Visual (VMC) · Day
Status
Completed · report September 22, 2017
Report
Approved by Office Director
NTSB office
General Aviation Accidents
Parties
FAA
FAA report
20170311001239A
Case key
94861

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 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 · 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.

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.

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
Reported as
Pipistrel Doo Ajdovscina Virus (SW)
Category
Glider
Serial number
621 SW 100
Built
2014
Airframe hours
103.5
Engine
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

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

As NTSB recorded them. NTSB leaves out names.

Role
Pilot
Age
74
Injuries
None
Certificates
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

Docket · 3

The files NTSB released with the investigation on August 22, 2017, on NTSB’s docket system: statements, records, photos and specialists’ reports. 4.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.