Monday, March 13, 2017

Incident occurred March 12, 2017 in Bend, Tehama County, California

Tehama County >> A bright yellow ultralight aircraft crash landed Sunday in the Bend area after a mechanical failure caused the aircraft to become unresponsive.

The pilot, Andrew Jessen, 74, of Anderson was not injured as a result of the crash.

Tehama County Sheriff’s Deputies were dispatched at 2:45 p.m. Sunday to a reported ultralight aircraft crash. The person who reported the incident said he saw the aircraft going down from his residence on Via Pasado in Red Bluff, according to a press release issued Monday by the Tehama County Sheriff’s Office.

The caller was in his personal vehicle attempting to locate the crash after speaking with dispatchers. Deputies arrived on scene at 2:57 p.m., when they met with Jessen and the caller.

Jessen said attempted to land the aircraft and was successful, but described the landing as “hard,” according to the release.

The Federal Aviation Administration was notified and spoke with deputies who were on scene. FAA personnel advised that there would be no investigation due to the fact that the aircraft is not registered and there were no injuries.

The amount of damage to the aircraft was not released as of noon Monday.

Original article can be found here:   http://www.redbluffdailynews.com

An Anderson man was not injured after the ultralight plane he was piloting suffered a mechanical failure and had to make a hard landing Sunday afternoon northeast of Red Bluff, authorities said.

The plane landed around 2:45 p.m. around Via Pasado Road in the Bend area.

Andrew Jessen, 74, said the mechanical issues the plane suffered caused the aircraft to become unresponsive, the Tehama County Sheriff’s said.

A resident in the area phoned emergency dispatchers around 2:45 p.m. to say he saw a bright yellow ultralight aircraft going down from his residence on Via Pasado.

Federal Aviation Administration authorities said there will be no investigation.

Story and comments: http://www.redding.com

Piper PA-28-181, N288PA, Bird Acquisition LLC: Accident occurred March 11, 2017 at Gila Bend Municipal Airport (E63), Maricopa County, Arizona

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

NTSB Identification: GAA17CA189 
14 CFR Part 91: General Aviation
Accident occurred Saturday, March 11, 2017 in Gila Bend, AZ
Probable Cause Approval Date: 09/22/2017
Aircraft: PIPER PA 28, registration: N288PA
Injuries: 3 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 flight instructor reported that he and two student pilots were on a night, visual flight rules, instructional flight. The instructor tried to activate the pilot-controlled lighting at the destination airport, but he believed that it was inoperative. He reported that he could see the windsock on the airfield but that he did not see the “X” near the runway numbers and performed a touch and go. During rotation the instructor reported that, “I heard a red cone make impact with the nose gear section.” He had to apply continuous forward pressure to the yoke because the nose continued to pitch up with the trim set to the full-down position. He asserted that the flight characteristics were “acceptable” and continued the flight about 47 nautical miles to their home airport. Upon arrival, the instructor alerted the tower that he had a stabilator malfunction and landed the airplane with zero flaps. The instructor reported that he did not check the notices to airmen (NOTAM). The airplane sustained substantial damage to the stabilator.

The pilot reported that there were no preaccident mechanical malfunctions or failures with the airplane that would have precluded normal operation. 
According to Federal Aviation Administration NOTAM 03/058, the airport runways were closed at the time of the accident.

The National Transportation Safety Board determines the probable cause(s) of this accident as follows:
The flight instructor’s failure to review the notices to airmen related to the airport, which resulted in his landing on a closed runway and the airplane striking runway closed markers. 

Additional Participating Entity:
Federal Aviation Administration / Flight Standards District Office: Scottsdale, Arizona

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

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

Bird Acquisition LLC: http://registry.faa.govN288PA

NTSB Identification: GAA17CA189
14 CFR Part 91: General Aviation
Accident occurred Saturday, March 11, 2017 in Gila Bend, AZ
Aircraft: PIPER PA 28, registration: N288PA
Injuries: 3 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 flight instructor reported that he and two student pilots were on a night, visual flight rules, instructional flight. The instructor tried to activate the pilot controlled lighting at the destination airport, but he believed that it was inoperative. He reported that he could see the wind sock on the airfield but he did not see the "X" near the runway numbers and performed a touch and go. During rotation the instructor reported that, "I heard a red cone make impact with the nose gear section." He had to apply continuous forward pressure to the yoke because the nose continued to pitch up with the trim set to the full down position. He asserted that the flight characteristics were "acceptable" and continued the flight about 47 nautical miles to their home airport. Upon arrival, the instructor alerted tower that he had a stabilator malfunction and landed the airplane with zero flaps. The instructor reported that he did not check the Notices to Airman. The airplane sustained substantial damage to the stabilator.

The pilot reported that there were no preaccident mechanical malfunctions or failures with the airplane that would have precluded normal operation. 

According to Federal Aviation Administration NOTAM 03/058, the airport runways were closed at the time of the accident.

Autogyro Cavalon, N425AG: Accident occurred March 10, 2017 at Santa Maria Public Airport (KSMX), Santa Barbara County, California

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

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

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

http://registry.faa.gov/N425AG

Federal Aviation Administration / Flight Standards District Office:  Van Nuys, California  

NTSB Identification: GAA17CA184
14 CFR Part 91: General Aviation
Accident occurred Friday, March 10, 2017 in Santa Maria, CA
Probable Cause Approval Date: 05/15/2017
Aircraft: CSP LEASING LLC CAVALON, registration: N425AG
Injuries: 1 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 student pilot reported that, during a stop-and-go landing in crosswind conditions, the gyroplane bounced about 4 ft. He added that the wind lifted the gyroplane and that he did not have “the speed or rudder control to counteract” the drift. The gyroplane impacted the ground on its right side.

The gyroplane sustained substantial damage to the empennage.

The student pilot reported that there were no preaccident mechanical failures or malfunctions with the airframe or engine that would have precluded normal operation.
A review of recorded data from the automated weather observation station located on the airport revealed that, about 39 minutes before the accident, the wind was from 300° at 8 knots. The gyroplane landed on runway 30.

The National Transportation Safety Board determines the probable cause(s) of this accident as follows:
The student pilot’s improper landing flare and subsequent failure to maintain crosswind correction during landing in crosswind conditions.




An experimental autogyro rotorcraft ended up on its side after a hard landing about 3 p.m. Friday at the Santa Maria Public Airport. 

“A small gyrocopter pilot was doing some touch and goes. He was only going about 10 mph. I don’t know if it was wind, or what, but he tipped over,” said Chris Hastert, Santa Maria Public Airport executive director.

“The monetary damage to the gyrocopter is probably pretty high, but the physical damage was fairly low," he added.

Airport crews were able to lift the aircraft and tow it off the airfield.

There were no injuries.

Airport officials will continue to investigate the incident.

Source:  http://lompocrecord.com

Cessna TR182 Turbo Skylane RG, Jetboy Helicopters LLC, N950RC: Incident occurred March 12, 2017 in Van Nuys, Los Angeles County, California

Jetboy Helicopters LLC: http://registry.faa.gov/N950RC

Federal Aviation Administration / Flight Standards District Office:  Van Nuys, California 

Aircraft on landing, nose gear collapsed. 

Date: 13-MAR-17
Time: 23:44:00Z
Regis#: N950RC
Aircraft Make: CESSNA
Aircraft Model: C182
Event Type: INCIDENT
Highest Injury: NONE
Aircraft Missing: No
Damage: UNKNOWN
Activity: UNKNOWN
Flight Phase: LANDING (LDG)
City: VAN NUYS
State: CALIFORNIA

Beech 76 Duchess, IASCO Flight Training Inc., N117JA: Incident occurred March 10, 2017 at Red Bluff Municipal Airport ( KRBL), Tehama County, California

IASCO Flight Training Inc:   http://registry.faa.gov/N117JA

Federal Aviation Administration / Flight Standards District Office: Sacramento, California 


Gear up landing. 

Date: 10-MAR-17
Time: 15:50:00Z
Regis#: N117JA
Aircraft Make: BEECH
Aircraft Model: 76
Event Type: INCIDENT
Highest Injury: NONE
Aircraft Missing: No
Damage: MINOR
Activity: PERSONAL
Flight Phase: LANDING (LDG)
Operation: 91
City: RED BLUFF
State: CALIFORNIA

Aircraft landed gear up and struck the propeller. 

Date: 10-MAR-17
Time: 15:50:00Z
Regis#: N117JA
Aircraft Make: BEECH
Aircraft Model: BE76
Event Type: INCIDENT
Highest Injury: NONE
Aircraft Missing: No
Damage: UNKNOWN
Activity: UNKNOWN
Flight Phase: LANDING (LDG)
City: RED BLUFF
State: CALIFORNIA

Bell 47G, N6359X: Incident occurred March 10, 2017 in Mojave, Kern County, California

http://registry.faa.gov/N6359X

Federal Aviation Administration / Flight Standards District Office:   Van Nuys, California 

Rotorcraft on landing, skid collapsed.

Date: 10-MAR-17
Time: 19:32:00Z
Regis#: N6359X
Aircraft Make: BELL
Aircraft Model: 47G
Event Type: INCIDENT
Highest Injury: NONE
Aircraft Missing: No
Damage: UNKNOWN
Activity: UNKNOWN
Flight Phase: LANDING (LDG)
City: MOJAVE
State: CALIFORNIA

JetBlue, Airbus A320-200, N658JB: Accident occurred March 12, 2017 in Fort Lauderdale, Broward County, Florida

JetBlue Airways Corp: http://registry.faa.gov/N658JB

Federal Aviation Administration / Flight Standards District Office:  Orlando, Florida 

Flight JBU1020,  aircraft encountered turbulence.  One (1) person on board sustained serious injury.   

Date: 12-MAR-17
Time: 23:31:00Z
Regis#: N658JB
Aircraft Make: AIRBUS
Aircraft Model: A320
Event Type: ACCIDENT
Highest Injury: SERIOUS
Aircraft Missing: No
Damage: NONE
Activity: COMMERCIAL
Flight Phase: EN ROUTE (ENR)
Operation: 121
Aircraft Operator: JETBLUE
Flight Number: JBU1020
City: FORT LAUDERDALE
State: FLORIDA

Alaska Airlines, Boeing 737-990ER, N493AS: Incident occurred March 10, 2017 at Logan International Airport (KBOS), Boston, Suffolk County, Massachusetts

Alaska Airlines Inc:   http://registry.faa.gov/N493AS

Federal Aviation Administration / Flight Standards District Office:   Boston, Massachusetts 

Flight ASA769, aircraft while at deicing pad, wing struck the deicing truck.  Taxied back to gate.  No injuries to persons on board.  Unknown injury to one (1)  person on ground.  

Date: 10-MAR-17
Time: 23:55:00Z
Regis#: N493AS
Aircraft Make: BOEING
Aircraft Model: B737
Event Type: INCIDENT
Highest Injury: UNKNOWN
Aircraft Missing: No
Damage: MINOR
Activity: COMMERCIAL
Flight Phase: TAXI (TXI)
Operation: 121
City: BOSTON
State: MASSACHUSETTS




BOSTON (CBS) – A worker was hurt after he fell from a bucket truck that tipped over on the tarmac at Logan Airport Friday night.

On a snowy evening at Terminal C, Massport says a de-icing truck and an Alaska Airlines plane came into contact. And what happened next had passengers calling for help.

“The wing hit the guy that was deicing the plane,” said passenger Scott Mather. “And the hose got wrapped up in his legs and pulled him off the cherry picker.”

“There was a dude in the basket there,” another passenger said. “He was dangling. He was dangling. It was unbelievable.”

The truck tipped over. A worker went tumbling to the ground.

“You could see under the plane the truck completely on its side with the bucket on the ground from where the man actually fell from,” said Michael Peter. “Maybe 20, 30 feet in the air.”

And passengers say a little 10-year-old boy was the first to call for help.

“There was an announcement and either the pilot or the stewardess got on and said ‘We want to thank this little 10-year-old boy,'” passenger David Fish said.

Those aboard the Boston to San Diego flight were evacuated, then put on buses and are landlocked for now.

But thankful the accident wasn’t worse.

“They’ve said luckily he’s safe,” Peter said. “So that’s the main thing.”

Story and video:  http://boston.cbslocal.com

Diamond DA-20-C1, N73YB: Incident occurred March 10, 2017 in Belgrade, Gallatin County, Montana

Yonder Blue Holdings  LLC:   http://registry.faa.gov/N73YB

Federal Aviation Administration / Flight Standards District Office: Helena, Montana

Aircraft on landing, went off the runway and struck a light. 

Date: 10-MAR-17
Time: 19:49:00Z
Regis#: N73YB
Aircraft Make: DIAMOND
Aircraft Model: DA20
Highest Injury: NONE
Aircraft Missing: No
Damage: NONE
Activity: INSTRUCTION
Flight Phase: LANDING (LDG)
City: BELGRADE
State: MONTANA

Piper Aerostar 602P, N301FW: Accident occurred March 11, 2017 at Reno/Tahoe International Airport (RNO), Reno, Nevada

The National Transportation Safety Board did not travel to the scene of this accident.

Federal Aviation Administration / Flight Standards District Office; Reno, Nevada


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/N301FW

Location: Reno, NV
Accident Number: WPR17LA076
Date & Time: 03/11/2017, 1515 PST
Registration: N301FW
Aircraft: PIPER AEROSTAR 602P
Aircraft Damage: Substantial
Defining Event: Landing gear not configured
Injuries: 1 None
Flight Conducted Under: Part 91: General Aviation - Business 

On March 11, 2017, about 1515 Pacific standard time, a Piper Aero Star 602P airplane, N301FW, landed with a retracted left main landing gear at the Reno/Tahoe International Airport (RNO), Reno, Nevada. The airline transport pilot was not injured; the airplane sustained substantial damage. The airplane was registered to and operated by the pilot under the provisions of Title 14 Code of Federal Regulations Part 91 for the personal cross-country flight. Visual meteorological conditions prevailed and an instrument flight rules flight plan was filed. The flight originated from Sandpoint Airport (SZT), Sandpoint, Idaho at 1100 and was destined for Minden-Tahoe Airport (MEV), Minden, Idaho.

The pilot reported that after departure from SZT the airplane performed normally in takeoff, climb and cruise flight; the gear up light illuminated after the gear retraction. As the flight approached MEV, the pilot entered a left traffic pattern for runway 30. He performed the landing checklist but only the nose landing gear (NLG) and the right main landing gear (MLG) indicator lights illuminated; the left MLG indicator light was not illuminated. The pilot initiated a climb and performed the procedures on the emergency gear extension checklist, however the left MLG indicator light did not illuminate. He contacted Reno Approach, declared an emergency and received permission to circle East of RNO to burn off fuel which is a part of the emergency gear up landing checklist. When fuel in the left wing tank was exhausted, he requested and received clearance to land on RWY 25. The airplane touched down with the left MLG retracted and the right MLG and the NLG extended. Before it came to a full stop, the airplane impacted two taxiway signs.

An airport operations supervisor, who communicated with the pilot over the radio as he attempted to land at MEV, reported that as the airplane flew over the runway, he observed only the NLG and the right MLG extended. The pilot announced that he would attempt to land on runway 30. The pilot executed two passes over the runway; both times it appeared to the supervisor that the left MLG was about 30o down from horizontal, and it appeared that the tire was sitting against the inside gear door.

The pilot reported to a Federal Aviation Administration (FAA) inspector who responded to the accident site, that the accident flight was the first flight after a recent owner assisted annual inspection. During the annual inspection a small amount of hydraulic fluid was found on the control valve located in the upper, forward part of the left landing wheel well. The valve was subsequently resealed with new "O" rings. The pilot stated he did not know if the landing gear was cycled subsequent to the valve maintenance. However, a review of maintenance records revealed that the last annual inspection, which was performed on March 6, 2017, included the landing gear swing.

The wreckage was recovered to a secure location for further examination. On March 27, 2017, the FAA inspector travelled to the wreckage location to assist in an examination and swing of the landing gear. The FAA inspector examined the airplane and noticed that the right MLG side brace was broken which would impede gear retraction. He decided to perform a partial swing of the landing gear to determine if the hydraulic system was operational. The gear pump circuit breaker was opened, and the gear handle was placed in the up position. The pump isolation switch was placed in the off position and the master switch was energized. The gear pump circuit breaker was reset, and the isolation switch was energized momentarily. The gear started to retract; however, immediately thereafter, the left side push-pull rod assembly that connects the gear door actuator to the landing gear and door control valve, failed due to what appeared to be previous damage. The push-pull rod failed in a compression load, crimped and eventually broke in half.

The FAA inspector found later that a mechanic had pictures of the left side rod that were taken prior to failure. The pictures showed postaccident damage of the push-pull rod.

The left main landing gear push-pull rod and the control valve were subsequently removed for additional examination. On June 21, 2017, the sequence valve was examined at Aerostar Aircraft Corporation, Hayden, Idaho. The valve was inspected, reassembled and tested in accordance with Aerostar Acceptance and/or Function Test Procedure. No malfunctions were noted with the valve. The push-pull rod was examined on July 13, 2017 at the National Transportation Safety Board material lab, Washington, D.C. The examined fracture surfaces were consistent with overload. Complete exam reports are appended to this accident in the public docket.

Pilot Information

Certificate: Airline Transport
Age: 55, Male
Airplane Rating(s): Multi-engine Land; Single-engine Land
Seat Occupied: Left
Other Aircraft Rating(s): None
Restraint Used: 3-point
Instrument Rating(s): Airplane
Second Pilot Present:
Instructor Rating(s): None
Toxicology Performed: No
Medical Certification: Class 3 With Waivers/Limitations
Last FAA Medical Exam: 06/05/2015
Occupational Pilot:
Last Flight Review or Equivalent: 06/15/2016
Flight Time:  2663 hours (Total, all aircraft), 111 hours (Total, this make and model), 2663 hours (Pilot In Command, all aircraft), 25 hours (Last 90 days, all aircraft), 13 hours (Last 30 days, all aircraft), 0 hours (Last 24 hours, all aircraft) 

Aircraft and Owner/Operator Information

Aircraft Make: PIPER
Registration: N301FW
Model/Series: AEROSTAR 602P 602P
Aircraft Category: Airplane
Year of Manufacture: 1981
Amateur Built: No
Airworthiness Certificate: Normal
Serial Number: 62P08838165018
Landing Gear Type: Retractable - Tricycle
Seats: 5
Date/Type of Last Inspection: 03/06/2017, Annual
Certified Max Gross Wt.: 6315 lbs
Time Since Last Inspection:
Engines: 2 Reciprocating
Airframe Total Time: 3959 Hours as of last inspection
Engine Manufacturer: Lycoming
ELT: C91  installed, not activated
Engine Model/Series: IO-540-AA1A5
Registered Owner: On file
Rated Power: 350 hp
Operator: On file
Operating Certificate(s) Held: None 

Meteorological Information and Flight Plan

Conditions at Accident Site: Visual Conditions
Condition of Light: Day
Observation Facility, Elevation: KRNO, 4400 ft msl
Distance from Accident Site: 1 Nautical Miles
Observation Time: 1555 PST
Direction from Accident Site: 189°
Lowest Cloud Condition: Few / 15000 ft agl
Visibility: 10 Miles
Lowest Ceiling: Broken / 25000 ft agl
Visibility (RVR):
Wind Speed/Gusts: 13 knots /
Turbulence Type Forecast/Actual: /
Wind Direction: 260°
Turbulence Severity Forecast/Actual: /
Altimeter Setting: 30.16 inches Hg
Temperature/Dew Point: 21°C / -3°C
Precipitation and Obscuration: No Obscuration; No Precipitation
Departure Point: SANDPOINT, ID (SZT)
Type of Flight Plan Filed: IFR
Destination: MINDEN, NV (MEV)
Type of Clearance: IFR
Departure Time: 1100 PST
Type of Airspace: Class C 

Airport Information

Airport: RENO/TAHOE INTL (RNO)
Runway Surface Type: Concrete
Airport Elevation: 4414 ft
Runway Surface Condition: Dry
Runway Used:25 
IFR Approach: None
Runway Length/Width: 6102 ft / 150 ft
VFR Approach/Landing: Straight-in

Wreckage and Impact Information

Crew Injuries: 1 None
Aircraft Damage: Substantial
Passenger Injuries: N/A
Aircraft Fire:None 
Ground Injuries:N/A 
Aircraft Explosion:None 
Total Injuries:1 None
Latitude, Longitude:39.499167, -119.768056 (est)

NTSB Identification: WPR17LA076
14 CFR Part 91: General Aviation
Accident occurred Saturday, March 11, 2017 in Reno, NV
Aircraft: PIPER AEROSTAR 602P, registration: N301FW
Injuries: 1 Uninjured.

This is preliminary information, subject to change, and may contain errors. Any errors in this report will be corrected when the final report has been completed. NTSB investigators may not have traveled in support of this investigation and used data provided by various sources to prepare this aircraft accident report.

On March 11, 2017, about 1515 Pacific standard time, a Piper Aero Star, N301FW, landed with a retracted left main landing gear at Reno/Tahoe International Airport (RNO), Reno, Nevada. The pilot, the sole occupant, was not injured; the airplane sustained substantial damage. The airplane was registered to and operated by the pilot under the provisions of Title 14 Code of Federal Regulations Part 91. Visual meteorological conditions prevailed for the cross-country flight, which operated on an instrument rules flight plan. The flight originated from Sandpoint Airport (SZT), Sandpoint, Idaho at 1100 with an intended destination of Minden-Tahoe Airport (MEV), Minden, Nevada.

The pilot reported that, during landing checks at MEV, the left main landing gear did not extend. However, the nose and the right main landing gear extended. The pilot elected to divert to RNO to land. Upon touchdown, the left main landing gear was still retracted. The airplane slid down the runway which resulted in a substantial damage to the left wing.

Xenos Motorglider, N56FD: Accident occurred March 11, 2017 at Minden–Tahoe Airport (KMEV), Minden, Douglas County, Nevada

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

NTSB Identification: GAA17CA190
14 CFR Part 91: General Aviation
Accident occurred Saturday, March 11, 2017 in Minden, NV
Probable Cause Approval Date: 11/14/2017
Aircraft: DAVIS FRANK R XENOS MOTORGLIDER, registration: N56FD
Injuries: 1 Minor.

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 of the tailwheel-equipped airplane reported that, during touchdown, the airplane “weathervaned to the left and full right rudder could not keep it on the runway.” Subsequently, the main landing gear dug into the soft mud, and the airplane nosed over. 
The airplane sustained substantial damage to the empennage.

The pilot reported that there were no preaccident mechanical malfunctions or failures with the airplane that would have precluded normal operation.
The automated weather observation system located on the accident airport reported that, about the time of the accident, the wind was variable at 6 knots. The pilot landed on runway 34.

The National Transportation Safety Board determines the probable cause(s) of this accident as follows:

The pilot’s failure to maintain directional control in variable wind conditions. 

Federal Aviation Administration / Flight Standards District Office: Reno, Nevada

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/N56FD

NTSB Identification: GAA17CA190
14 CFR Part 91: General Aviation
Accident occurred Saturday, March 11, 2017 in Minden, NV
Aircraft: DAVIS FRANK R XENOS MOTORGLIDER, registration: N56FD
Injuries: 1 Minor.

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 of the tailwheel-equipped airplane reported that, during touchdown the airplane "weathervaned to the left and full right rudder could not keep it on the runway". Subsequently, the main landing gear dug into the soft mud and the airplane nosed over.

The airplane sustained substantial damage to the empennage.

The pilot reported that there were no preaccident mechanical malfunctions or failures with the airplane that would have precluded normal operation.

The automated weather observation system located on the accident airport reported that, about the time of the accident, the wind was variable at 6 knots. The pilot landed on runway 34.

Eclipse 10, N507EA: Incident occurred February 27, 2018 in Rio Rancho, Sandoval County New Mexico -and- Incident occurred March 10, 2017 in Belen, Valencia County, New Mexico

Federal Aviation Administration / Flight Standards District Office: Albuquerque, New Mexico

Gyrocopter experienced engine failure and landed on a road. 

http://registry.faa.gov/N507EA

Date: 27-FEB-18
Time: 20:38:00Z
Regis#: N507EA
Aircraft Make: EXPERIMENTAL
Aircraft Model: ECLIPSE 10
Event Type: INCIDENT
Highest Injury: NONE
Aircraft Missing: No
Damage: NONE
Activity: UNKNOWN
Flight Phase: UNKNOWN (UNK)
Operation: 91
City: RIO RANCHO
State: NEW MEXICO

March 10, 2017:   Gyrocopter on landing, tipped over.

Date: 10-MAR-17
Time: 20:00:00Z
Regis#: N507EA
Aircraft Make: EXPERIMENTAL ECLIPSE
Aircraft Model: ECLIPSE 10
Event Type: INCIDENT
Highest Injury: NONE
Aircraft Missing: No
Damage: MINOR
Activity: UNKNOWN
Flight Phase: LANDING (LDG)
City: BELEN
State: NEW MEXICO

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.

Cessna 172M Skyhawk, Twin Oaks Airpark Inc., N5440H: Accident occurred March 12, 2017 at Stark's Twin Oaks Airpark (7S3), Hillsboro, Washington County, Oregon

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

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


Aviation Accident Data Summary - National Transportation Safety Board: https://app.ntsb.gov/pdf

Twin Oaks Airpark Inc: http://registry.faa.gov/N5440H


Additional Participating Entity:

Federal Aviation Administration / Flight Standards District Office: Hillsboro, Oregon

NTSB Identification: GAA17CA186 
14 CFR Part 91: General Aviation
Accident occurred Sunday, March 12, 2017 in Hillsboro, OR
Probable Cause Approval Date: 06/07/2017
Aircraft: CESSNA 172, registration: N5440H
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, during the landing roll with a “light quartering tailwind,” the airplane veered off the runway to the left into soft mud and nosed over.
The vertical stabilizer and rudder sustained substantial damage.

The pilot reported that there were no preaccident mechanical malfunctions or failures with the airplane that would have precluded normal operation.

The nearest automated weather observation station, located 7 nautical miles from the accident airport, about the time of the accident, recorded variable wind at 5 knots. The pilot reported that he landed on runway 2.

The National Transportation Safety Board determines the probable cause(s) of this accident as follows:
The pilot's failure to maintain directional control during the landing roll in quartering tailwind conditions.

The pilot reported that during the landing roll with a "light quartering tailwind," the airplane veered off the runway to the left into soft mud and nosed over.

The vertical stabilizer and rudder sustained substantial damage.

The pilot reported that there were no preaccident mechanical malfunctions or failures with the airplane that would have precluded normal operation.

The nearest automated weather observation station 7 nautical miles from the accident airport, about the time of the accident, recorded variable wind at 5 knots. The pilot reported that he landed on runway 2.

Schweizer SGS 1-26E, Aero Club Albatross Inc., N17933: Accident occurred March 11, 2017 in Bangor, Northampton County, Pennsylvania

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

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

Aviation Accident Data Summary - National Transportation Safety Board: https://app.ntsb.gov/pdf

Additional Participating Entity:
Federal Aviation Administration / Flight Standards District Office: Allentown, Pennsylvania

Aero Club Albatross Inc: http://registry.faa.gov/N17933

NTSB Identification: GAA17CA196
14 CFR Part 91: General Aviation
Accident occurred Saturday, March 11, 2017 in Bangor, PA
Probable Cause Approval Date: 06/07/2017
Aircraft: SCHWEIZER SGS126, registration: N17933
Injuries: 1 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 glider pilot reported that, while returning to his home airport, he was unable to find enough lift and did not have enough altitude to cross a section of land called “The Gap.” After he altered course to land at an alternate airport, he attempted to ridge soar but again did not encounter enough lift. He “hugged the ridge top” for as long as he could and then proceeded down a valley in anticipation of landing in a field. Subsequently, the glider collided with trees preceding the field and came to rest suspended in the trees.

The glider sustained substantial damage to both wings and empennage. 
The pilot reported that there were no preaccident mechanical failures or malfunctions with the glider that would have precluded normal operation.

The National Transportation Safety Board determines the probable cause(s) of this accident as follows:
The glider’s encounter with atmospheric conditions where the lift was not sufficient to maintain flight, which resulted in an off-airport landing. 

The glider pilot reported that while returning to his home airport, he was unable to find enough lift, and did not have enough altitude to cross a section of land called "The Gap". After he altered course to land at an alternate airport he attempted to ridge soar, but was again unable to encounter enough lift. He "hugged the ridge top" for as long as he could and then proceeded down a valley in anticipation of landing in a field. Subsequently, the glider collided with trees prior to the field and came to rest suspended in the trees.

The glider sustained substantial damage to both wings and empennage. 

The pilot reported that there were no pre-accident mechanical failures or malfunctions with the glider that would have precluded normal operation.