Aircraft
Make / model- Manufacturer
- PIPISTREL DOO AJDOVSCINA
- Model
- VIRUS SW
- Type
- Fixed wing single engine
- Category
- Land
- Engines
- 1 × ROTAX 912ULS2
- Seats
- 2
- Year
- 2014
N345M
FAA · N-Number United StatesV Valid Registration On watch list Updated
- Mode-S hex
-
A3D0F4 - Serial
- 621 SW 100
- Type
- Fixed wing single engine
- Manufacturer
- PIPISTREL DOO AJDOVSCINA
- Model
- VIRUS SW
- Year
- 2014
Overview
Registrant
MASTER
Individual
ROGERS RAYLON R DBA
Live tracking
Mode-S
Mode-S hex code (24-bit ICAO)
A3D0F4
This is the unique transponder address this airframe broadcasts. It does not change when the registration changes hands.
Key dates
Lifecycle2014
Manufactured
Airworthy
Last action
Recent changes
Members onlyChange history for this aircraft is available to signed-in members. See what's included.
Market intelligence
Members onlyMarket-intelligence filings (FAA registrations only) are available to signed-in members. See what's included.
Technical
Airframe
ACFTREF- Manufacturer
- PIPISTREL DOO AJDOVSCINA
- Model
- VIRUS SW
- Type aircraft
- Fixed wing single engine
- Category
- Land
- Weight class
- Light
- Year mfr
- 2014
- Serial number
- 621 SW 100
Powerplant
ENGINE ref- Manufacturer
- ROTAX
- Model
- 912ULS2
- Type
- 4 Cycle
- # of engines
- 1
- Horsepower
- 100 hp
Capacity & weight
Performance- Seats
- 2
- Weight class
- Light
FAA uses a weight category code rather than exact pounds. Weight classifications reflect the aircraft type certificate data.
Registration
Status
Current
V
Valid Registration
Last action by FAA .
Certificate
Airworthiness- Type registrant
- Individual
- Airworthiness
- 443
- Airworthy since
- Last FAA action
- Fractional owner
- No
- FAA region
- Southwestern
Registrant
MASTER address
Active
- Owner name
-
ROGERS RAYLON R DBA
Registered to an FAA-certificated dealer → view profile - Type
- Individual
- Street
- 930849 SOUTH 3370 ROAD
- City
- WELLSTON, OK 74881
- County
- 081
- Country
- United States
Safety
Safety records
1 on file
1
NTSB records on file
11 Mar 2017
Most recent record
None
Highest injury level
Substantial
Worst aircraft damage
-
14:10 UTC GAA17CA185 NTSB Accident Location: Okmulgee, OK, USA Injury: None Damage: Substantial
Record details
- Record match
- N-number and serial number match
- Aircraft
- PIPISTREL DOO AJDOVSCINA VIRUS SW
- Occurrence
- Prior to flight Preflight or dispatch event
- Operation
- Part 91 — General aviation
- Conditions
- VMC · Day · Wind 40° at 11 kt · Visibility 10 sm
- Accident 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. - Factual 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. - Cause narrative
- 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
- Personnel issues-Task performance-Planning/preparation-(general)-Pilot - C; 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
- Official record
- View NTSB docket
Full safety record preview
Showing 1 of 1 indexed NTSB records for N345M. Create a free account to view all matched records.
Safety records are matched from official aviation occurrence datasets, with serial/model context shown where available. This is an indexed record check, not an exhaustive safety record. Artifact built .