Monday, March 13, 2017

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

NTSB Identification: GAA17CA189 14 CFR Part 91: General AviationAccident occurred Saturday, March 11, 2017 in Gila Bend, AZProbable Cause Approval Date: 09/22/2017Aircraft: PIPER PA 28, registration: N288PAInjuries: 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.

Bird Acquisition LLC: http://registry.faa.govN288PANTSB Identification: GAA17CA18914 CFR Part 91: General AviationAccident occurred Saturday, March 11, 2017 in Gila Bend, AZAircraft: PIPER PA 28, registration: N288PAInjuries: 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.

http://registry.faa.gov/N425AGFederal Aviation Administration / Flight Standards District Office: Van Nuys, California NTSB Identification: GAA17CA18414 CFR Part 91: General AviationAccident occurred Friday, March 10, 2017 in Santa Maria, CAProbable Cause Approval Date: 05/15/2017Aircraft: CSP LEASING LLC CAVALON, registration: N425AGInjuries: 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

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

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

Aviation Accident Preliminary Report - National Transportation Safety Board: https://app.ntsb.gov/pdfFederal Aviation Administration / Flight Standards District Office; Reno, Nevadahttp://registry.faa.gov/N301FWNTSB Identification: WPR17LA07614 CFR Part 91: General AviationAccident occurred Saturday, March 11, 2017 in Reno, NVAircraft: PIPER AEROSTAR 602P, registration: N301FWInjuries: 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.

NTSB Identification: GAA17CA19014 CFR Part 91: General AviationAccident occurred Saturday, March 11, 2017 in Minden, NVProbable Cause Approval Date: 11/14/2017Aircraft: DAVIS FRANK R XENOS MOTORGLIDER, registration: N56FDInjuries: 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/pdfInvestigation Docket - National Transportation Safety Board: https://dms.ntsb.gov/pubdms

http://registry.faa.gov/N56FDNTSB Identification: GAA17CA19014 CFR Part 91: General AviationAccident occurred Saturday, March 11, 2017 in Minden, NVAircraft: DAVIS FRANK R XENOS MOTORGLIDER, registration: N56FDInjuries: 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.

NTSB Identification: GAA17CA185 14 CFR Part 91: General AviationAccident occurred Saturday, March 11, 2017 in Okmulgee, OKProbable Cause Approval Date: 09/22/2017Aircraft: PIPISTREL DOO AJDOVSCINA VIRUS, registration: N345MInjuries: 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.

http://registry.faa.gov/N345MNTSB Identification: GAA17CA185 14 CFR Part 91: General AviationAccident occurred Saturday, March 11, 2017 in Okmulgee, OKAircraft: PIPISTREL DOO AJDOVSCINA VIRUS, registration: N345MInjuries: 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.

NTSB Identification: GAA17CA186 14 CFR Part 91: General AviationAccident occurred Sunday, March 12, 2017 in Hillsboro, ORProbable Cause Approval Date: 06/07/2017Aircraft: CESSNA 172, registration: N5440HInjuries: 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.

Aero Club Albatross Inc: http://registry.faa.gov/N17933NTSB Identification: GAA17CA19614 CFR Part 91: General AviationAccident occurred Saturday, March 11, 2017 in Bangor, PAProbable Cause Approval Date: 06/07/2017Aircraft: SCHWEIZER SGS126, registration: N17933Injuries: 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.