Monday, March 13, 2017

Pipistrel Virus SW, N345M: Accident occurred March 11, 2017 at Okmulgee Regional Airport (KOKM), Oklahoma -and- Incident occurred November 01, 2015 near Orlando Executive Airport (KORL), Florida

Aviation Accident Final Report - National Transportation Safety Board: https://app.ntsb.gov/pdf 

NTSB Identification: GAA17CA185 
14 CFR Part 91: General Aviation
Accident occurred Saturday, March 11, 2017 in Okmulgee, OK
Probable Cause Approval Date: 09/22/2017
Aircraft: PIPISTREL DOO AJDOVSCINA VIRUS, registration: N345M
Injuries: 2 Uninjured.

NTSB investigators used data provided by various entities, including, but not limited to, the Federal Aviation Administration and/or the operator and did not travel in support of this investigation to prepare this aircraft accident report.

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.

The National Transportation Safety Board determines the probable cause(s) of this accident as follows:
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.

Additional Participating Entity:
Federal Aviation Administration / Flight Standards District Office: Oklahoma City, Oklahoma

Aviation Accident Factual Report - National Transportation Safety Board:  https://app.ntsb.gov/pdf

Investigation Docket - National Transportation Safety Board: https://dms.ntsb.gov/pubdms

http://registry.faa.gov/N345M

NTSB Identification: GAA17CA185 
14 CFR Part 91: General Aviation
Accident occurred Saturday, March 11, 2017 in Okmulgee, OK
Aircraft: PIPISTREL DOO AJDOVSCINA VIRUS, registration: N345M
Injuries: 2 Uninjured.

NTSB investigators used data provided by various entities, including, but not limited to, the Federal Aviation Administration and/or the operator and did not travel in support of this investigation to prepare this aircraft accident report.

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 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 force landed in the waters of Lake Orlando on November 1st, 2015.

Officials say the pilot had some kind of issue with his plane and he had to land it in Lake Orlando.

The pilot was about to get out of the plane on his own and walk to shore. He was not injured in the landing.

Officials said no fuel leaked in the lake and there is no environmental hazard. They do not have know what went wrong with his plane yet.

The Federal Aviation Administration will investigate the incident on November 2nd, 2015.

No comments: