Pipistrel Doo Ajdovscina VIRUS N345M

Summary

On 11 March 2017 at about 14:10 local time, a Pipistrel Doo Ajdovscina VIRUS registered N345M was involved in an accident near Okmulgee, Oklahoma, United States. 2 people were on board and nobody was injured. The aircraft was substantially damaged. The NTSB has published a probable cause for this accident; it is quoted in full below.

Date

11 March 2017 at 14:10

Classification

Accident

Location

Okmulgee, Oklahoma, United States

Nearest airport

Okmulgee Rgnl (OKM)

Coordinates

35.6650, -95.9461

Aircraft

Pipistrel Doo Ajdovscina VIRUS

Registration

N345M

Category

Glider

Year built

2014

Engines

1

Operator

Not recorded

Operating rule

Part 91: General Aviation

Purpose of flight

Personal

Phase of flight

Not recorded

Route

Wellston → Okmulgee

Aircraft damage

Substantial

Weather

VMC

Light

Day

NTSB number

GAA17CA185

Nobody was injured.

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.

Quoted verbatim from the NTSB record. This site does not paraphrase or interpret it.

Read the full NTSB narrative

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.

Quoted verbatim from the NTSB record.