Pipistrel DOO Ajdovscina VIRUS accident near Okmulgee, Oklahoma, March 11, 2017
On March 11, 2017 at about 2:10 pm local time, a 2014 Pipistrel DOO Ajdovscina VIRUS (glider), registered N345M, was substantially damaged in an accident during landing (landing roll) near Okmulgee, Oklahoma (Okmulgee Rgnl airport). It was a personal flight under general aviation rules (Part 91). No one was hurt; 2 people were on board or involved. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
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.
Source: NTSB aviation accident database, copy made November 2, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- March 11, 2017 · about 2:10 pm local time · cases in 2017
- Place
- Okmulgee, Oklahoma · Okmulgee Rgnl · cases near this airport · map
- Type
- Accident
- Injuries
- No one was hurt; 2 people were on board or involved.
- Weather
- visual conditions (good weather)
- Aircraft
- Pipistrel DOO Ajdovscina VIRUS SW, built 2014
- Registration
- N345M · registry record · serial 621 SW 100
- Damage
- Substantial damage
- Flight
- Personal flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
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 complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.
The factual record from the NTSB's investigation tables, in plain English
What happened, in order
- Preflight or dispatch event during prior to flight
- Miscellaneous/other during landing (landing roll) defining event
The NTSB's findings
- cause Personnel issues › Task performance › Planning/preparation › (general) › Pilot
- Environmental issues › Physical environment › Object/animal/substance › Fence/fence post › Effect on equipment
- Environmental issues › Operating environment › Airport facilities/design › Runway markings/signage › Effect on operation
Pilot
- Certificate: flight instructor, commercial pilot
- Ratings: multi-engine land; single-engine land; instructor: airplane single-engine; rotorcraft: glider
- Flight time: 8,500 hours in all; 50 in this make and model; 50 in the last 90 days; 8,400 as pilot in command; 2,500 on instruments
- Last flight review: August 5, 2016
- Medical certificate: Class 2 (with waivers/limitations)
- Seat: left
- Injury: no injuries
The aircraft
- Airframe total time: 103.5 hours
- Last inspection: condition inspection, July 12, 2016
- Maximum gross weight: 1,323 lb
- Seats: 2
- Landing gear: fixed
- Engine: Rotax 912 ULS (piston); 104 hours total
The flight
- Departed from: 43OK Wellston OK at 1:40 pm
- Destination: OKM Okmulgee OK
- Flight plan: none
Weather at the time
- Light: daylight
- Wind: from 040° at 11 knots, gusting 15
- Visibility: 10 statute miles
- Sky: overcast at 3,500 ft
- Temperature: 43°F (6°C), dew point 41°F (5°C)
- Altimeter: 30.22 inHg
- Observation at 1:55 pm from KOKM
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 | |||
| Passengers | 1 |
Photographs from the investigation 1 picture from the NTSB's docket, as the NTSB released them
The NTSB's photographs with the NTSB's captions, at screen size. Open a picture to see it full size or to report one that should not be shown.
Documents from the investigation the NTSB's docket: the evidence folder behind the report
3 documents, released by the NTSB on August 22, 2017. View them here, or download them; the NTSB redacts some personal details before release, and this site shows the NTSB's own titles rather than its file names.
| # | Document | What it is | |
|---|---|---|---|
| 1 | Pilot/operator Aircraft Accident Report, NTSB Form 6120.1 | PDF, 9 pages | View Download |
| 2 | Okmulgee Rgnl Chart Supplement | PDF, 1 page | View Download |
| 3 | Accident Photo | PDF, 1 page · our copy | View Download |
The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.
Other NTSB records under N345M the same tail number, which may have belonged to a different aircraft at the time
Connections how this case links to the rest of the register
- N345M on the register today · the tail number may have moved to another aircraft since
- Engine: Rotax 912 ULS 62 aircraft carry this series today · as the NTSB recorded it
- Okmulgee Rgnl/Paul And Betty Abbott Field · nearest airport
- Accidents and incidents in Oklahoma 1,300 since 1982 · 181 in the last ten years
- Oklahoma 5,658 aircraft registered
- Other NTSB records under N345M 1 records · the number may have belonged to another aircraft at the time
The whole map of how records connect · these connections as data: /graph/accident/GAA17CA185.json.
The bigger picture in Aviation Analytics: accidents over time since 1982, by model, by phase of flight and conditions, by place and on the map.
Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text does not name anyone involved, its policy at this time. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.