Wednesday, March 2, 2016

JOINT BASE MCGUIRE-DIX-LAKEHURST - The FAA is investigating after a military KC-10 refueling jet was hit by a laser Tuesday while flying a training mission over the Jersey shore, officials said.The flight crew reported a green laser illuminated the plane at 10:20 p.m. at an altitude of 4,000 feet in the Chatsworth area of Lacey Township, Ocean County, FAA spokesman Jim Peters said. The FAA notified the Lacey police department.The KC-10 was from the 514th Air Mobility Wing, a reservist refueling wing operating from the Joint Base, said wing spokeswoman Master Sgt. Donna Jeffries.Jeffries said the crew reported a "momentary flash" and was able to avert their eyes.While a potentially dangerous situation, this event turned out to be a minor incident and the massive tanker jet returned safely to the base, she said. The KC-10 was about 15 miles away when the laser illumination occurred, Jeffries said.Laser incidents are rare with military aircraft, she said. In the past five years, she said only one other incident has occurred with the wing, Jeffries said.In July, a dozen aircraft over New Jersey skies reported dangerous laser beams crossing their paths in a single night. A Coast Guard aircraft over Ocean City, Cape May County was among those affected.Shining a laser into an aircraft cockpit is a federal crime with potential jail time and fines.Nearly 3,900 laser-aircraft incidents were reported nationwide in 2014, up from roughly 2,800 in 2010, according to FAA data.Original article can be found here: http://www.nj.com

A former WestJet flight attendant who said she was fired for making waves after being sexually assaulted by a pilot was actually let go for performance issues, according to the airline.
WestJet has filed a statement of defence in response to Mandalena Lewis’s lawsuit that outlines eight disciplinary actions allegedly brought against her between 2008 and 2014.Issues cited include missed shifts and one incident where a captain accused her and other attendants of drinking alcohol before a flight, resulting in its cancellation.The airline said Lewis was ultimately fired in January 2016 after she sent an email to her superiors that contained an expletive.“Lewis’s grossly insubordinate and insolent email, combined with Lewis’s extensive disciplinary record, warranted the termination of Lewis’s employment for just cause,” WestJet’s claim reads.In her lawsuit, Lewis alleges she was on short-term disability leave for growing anxiety relating to her sexual assault and the airline’s response when she was let go.She said her email was a frustrated demand for answers, which she sent after repeatedly asking WestJet for files outlining what investigation, if any, had been undertaken in response to her allegations against the pilot.

WestJet denies knowing the request had to do with that, claiming Lewis only requested her own employment file and “at no time” indicated it had to do with her complaint.Her email, according to WestJet, read: “Where the fuck is my usb card with my file on it. It has been 90 days since I requested them. Fed ex it asap.”Lewis claims her assault took place during a Hawaiian layover in January 2010, when a pilot, identified only as “Pilot M.” in her suit, dragged her onto a bed and groped her after they had been drinking in his hotel room. Several other women have recently raised allegations against the same man.Her lawsuit accuses the airline of failing to properly investigate what happened, and even altering Pilot M.’s flying schedule so he could avoid prosecution in the state.CTV News has confirmed that Maui prosecutors are still waiting to serve the pilot with a court summons.In WestJet’s statement of defence, the airline said it “immediately assisted Lewis upon her return home from Maui by removing her from the rest of her scheduled shift, offering her support, and encouraging her to report the allegations to the Maui police.”It added that a full investigation was conducted, but couldn’t determine Pilot M. had committed an assault.WestJet said the investigation did, however, find the pilot had violated its standards of conduct, which bars excessive drinking and fraternizing with flight attendants, and he was suspended.He was further disciplined by being removed from the Extended-Range Twin-Engine Operations, or ETOPS, which allows pilots to fly international routes, according to the airline.Pilot M. was eventually re-admitted to ETOPS, WestJet added, and has since flown to Maui.The airline has asked that Lewis’s claim be dismissed and that it be awarded costs.None of the allegations in the lawsuit have been proven in court.Since CTV News broke the story about Lewis’s allegations, more than a dozen other WestJet employees have come forward with claims of sexual assault and harassment, including some that are against Pilot M.WestJet said it has heard from several workers who have raised new allegations and the company has hired Ernst & Young to investigate. http://bc.ctvnews.ca

Mandalena Lewis claims she was sexually assaulted by a WestJet pilot in January 2010, while she working as a flight attendant for the airline.

A former WestJet flight attendant who claims she was sexually assaulted by a pilot has launched a lawsuit alleging the airline failed to properly investigate what happened.Vancouver resident Mandalena Lewis, who agreed to have her name publicized in the interest of sharing her story, said the assault took place while she was on a layover at a Hawaiian hotel in January 2010.According to her civil claim, which was filed in B.C. Supreme Court this week, she met a WestJet pilot identified only as “Pilot M” in his room, where he dragged her onto a bed and proceeded to kiss and grope her against her will."She resisted physically, yelling that he stop," her claim reads. "Pilot M did not stop but rather continued to grope and attempt to kiss her.”Lewis said she was eventually able to fight him off and leave.Her claim alleges she reported the incident to WestJet shortly after, but the airline “failed to adequately investigate” her allegations.“All that WestJet did was structure [her] work schedule so that she did not have to work with the pilot,” it reads.“She was told to keep quiet about the incident notwithstanding that other female flight attendants were working under the pilot.”Lewis said she was even more distressed after talking to another flight attendant, who claimed to have been sexually assaulted by the same pilot two years earlier.Her lawsuit alleges that “WestJet knew at least by 2008 that the pilot was a danger to other employees and WestJet had failed to remove him from the workplace.”She said she demanded WestJet explain what investigation, if any, had been undertaken, but was left waiting for a response. Lewis later went on short-term disability leave for growing anxiety, according to her suit, and was eventually fired after emailing the company to express her frustration at the lack of answers.Her suit alleges the airline’s conduct was negligent and breached her employment contract, and that her firing was a “retaliation.”WestJet has yet to file a statement of defence in the case, but told CTV News on Wednesday that it takes the safety of its employees seriously.“WestJet does not comment on ongoing legal proceedings but confirms it will file a statement of defense in which it will vigorously defend the allegations contained in the claim,” a spokesperson said in an email.“WestJet further confirms its commitment to maintaining a safe and harassment free environment for its employees and guests and takes its obligations in this respect with the utmost seriousness.”None of the claims against the airline have been proven in court. Lewis's allegations were investigated by police in Hawaii; a Maui prosecutor confirmed to CTV News that a WestJet pilot was charged in the state in 2010.Original article can be found here: http://bc.ctvnews.ca

Frontier Airlines said Thursday it has applied to the U.S. Transportation Department to begin a once-a-week nonstop flight between Philadelphia and Varadero, Cuba. Frontier, which has been expanding at Philadelphia International Airport, also proposed a one-stop flight in Miami from Philadelphia to both Santa Clara and Camaguey, Cuba, using 180-seat Airbus A320 aircraft.Frontier will fly this summer to 20 destinations from Philadelphia, effective June 1.American Airlines, which has a hub and 76 percent of the flights in Philadelphia, did not apply for direct Cuba passenger flights from Philadelphia. American instead chose its hubs in Miami, Dallas Fort Worth, Charlotte, Los Angeles, and Chicago to begin new nonstop Cuba scheduled service.Original article can be found here: http://www.philly.com

Terre Haute International Airport-Hulman Field is a community asset worth nurturing. Sizable public investments have been made at the facility through the years, and significant upgrades have allowed it to remain a viable centerpiece for economic development in the region.It hasn’t been easy, of course. Once upon a time, the airport bustled with activity as passenger planes flew in and out several times a day, an air-freight operation made it a shipping hub, and the 181st Fighter Wing and its fleet of F-16s provided flash and fanfare. Times changed, however, and usage decreased through the years while airport officials tried to find new ways to stimulate activity.Despite long-standing challenges, local officials are staying focused on the future and working on making the airport better and more productive for the community and its taxpayers.Last week, airport officials unveiled improvement plans they hope will revitalize interest and usage of airport facilities. Included in the plan is an exterior upgrade to a terminal building, conversion of a runway into a taxiway that will allow the addition of more hangars and business development, and the addition of a non-scheduled public charter passenger service.Each element to the plan is important, but the runway renovation and conversion holds great potential for business development on site. “Our ultimate goal is we are looking for new industry,” said Jeff Hauser, the airport’s executive director.The more than $3.8 million runway project will be done in phases over the next three years and paid for mostly by the Federal Aviation Administration.We applaud airport officials and the board for continuing efforts to make the facility viable for aviation and business development. The airport is a resource that requires ongoing attention and support.Original article can be found here: http://www.tribstar.com/opinion/editorials

American Airlines applied Wednesday for permission to fly nonstop from Charlotte to Havana, in a landmark move as air carriers and the U.S. government look to reestablish ties with Cuba.American wants to fly once a day year-round from Charlotte, its second-busiest hub, where American operates about 90 percent of daily flights. The carrier also applied for 10 daily flights to Havana from Miami, its primary gateway to Latin America and the Caribbean, as well as once daily from Dallas/Fort Worth and weekly from Los Angeles and Chicago.Charlotte’s flight is ranked eighth on the priority list of routes that American wants to fly to Cuba, behind seven of the Miami flights.“American’s proposed service – from Miami and four other hubs – will provide a strong foundation for the sustained future growth of commercial and cultural ties between the U.S. and Cuba,” American chief executive Doug Parker said in a statement.All flights now operating between the U.S. and Cuba are charters. The Department of Transportation – headed by former Charlotte Mayor Anthony Foxx – will review the applications from American and other carriers and decide which to grant.The other airlines applying for Cuba flights, originating from various U.S. cities, include Delta, United, JetBlue and Southwest. Scheduled flights could begin in the fall.In its application, American said its Charlotte service would complement its Miami routes, offering 34 destinations for connecting passengers in Charlotte not offered through the Miami hub. A flight from Charlotte to Havana would also give connecting passengers from other cities another option, since many of the flights from Miami are expected to be filled by local demand.The proposed Charlotte-Havana flight would take about 2 1/2 hours and cover 847 miles, according to American’s application. It would be on an Airbus A319, a jet that seats 144 passengers total, with eight in business class.President Barack Obama has led an effort to normalize relations, commerce and travel between the U.S. and Cuba. The U.S. has blacklisted Cuba with a commercial embargo and travel restrictions for more than five decades, since the communist regime came to power under Fidel Castro.The Castro regime remains in place, under President Raul Castro, but relations have warmed up sharply in the past year, despite continuing opposition in the U.S. led by congressional Republicans. Obama plans to visit Cuba this month, the first such trip by a sitting U.S. president in more than 80 years.Foxx, the transportation secretary, signed an agreement with Cuba last month that will allow regular, scheduled air service between the two countries to formally resume. The airlines’ proposed routes must also be approved by Cuban authorities.Even if the Charlotte flight is approved, however, it won’t immediately be possible for Charlotteans to hop on a plane and head to Havana. Travel restrictions still in place require that U.S. citizens can only go to Cuba for certain types of trips, such as educational tours organized by approved companies, family visits, religious or charitable activities or journalistic activity.An estimated 160,000 American leisure travelers visited Cuba last year, as well as hundreds of thousands of Cuban-Americans visiting family. Regular commercial air travel could add hundreds of thousands of leisure travelers.Original article can be found here: http://www.charlotteobserver.com

NTSB Identification: WPR16LA07914 CFR Part 91: General AviationAccident occurred Wednesday, March 02, 2016 in Fountain Hills, AZProbable Cause Approval Date: 05/23/2017Aircraft: PIPER PA 22-150, registration: N4356AInjuries: 2 Uninjured.NTSB investigators may not have traveled in support of this investigation and used data provided by various sources to prepare this aircraft accident report.The private pilot reported that, after a preflight inspection and engine run-up revealed no anomalies, he and a passenger departed, circled a nearby mountain, then descended to an altitude about 750 ft above ground level. Shortly thereafter, the engine experienced a partial loss of power. The pilot attempted to restore engine power, but was unsuccessful, and he elected to land the airplane on a dry wash. As the airplane touched down, the right main landing gear sank into the dirt, and the airplane made a sharp turn to the right. The airplane impacted a tree and came to rest nose down. The atmospheric conditions at the time of the accident were not conducive to the formation of carburetor icing. A postaccident engine examination and test run revealed no anomalies that would have precluded normal operation; therefore, the reason for the loss of partial engine power could not be determined.The National Transportation Safety Board determines the probable cause(s) of this accident as follows:A partial loss of engine power for reasons that could not be determined because postaccident examination did not reveal any anomalies that would have precluded normal operation.

http://registry.faa.gov/N4356ANTSB Identification: WPR16LA07914 CFR Part 91: General AviationAccident occurred Wednesday, March 02, 2016 in Fountain Hills, AZAircraft: PIPER PA 22-150, registration: N4356AInjuries: 2 Uninjured.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 2, 2016, about 1600 mountain standard time, a Piper PA-22-150 airplane, N4356A, executed a precautionary landing onto a sandy wash following a partial loss of engine power near Fountain Hills, Arizona. The private pilot and passenger were not injured; and the airplane sustained substantial damage to the wings. The airplane was registered to, and operated by, a private party as a 14 Code of Federal Regulations Part 91 personal flight. Visual meteorological conditions prevailed at the time of the accident, and no flight plan was filed. The local flight originated from Phoenix-Mesa Gateway Airport (IWA), Phoenix, Arizona at about 1540.The pilot reported that after a normal preflight and run-up, he took off and circled a nearby mountain before descending to about 750 feet above the ground at a 2,400 RPM. As they followed a nearby river, the engine started to sputter and decrease to about 900 RPM; the pilot increased and decreased the throttle several times, but the engine never went above 1,200 RPM before it decreased again. He observed that the oil pressure was low; therefore, he attempted to switch fuel tanks, turned on carb heat, ensured the mixture was full rich, but the engine never responded. The pilot elected to land the airplane onto a dry wash. When the airplane touched down, the right main landing gear sunk into the dirt and the airplane made a sharp turn to the right. The airplane rolled along the dirt, impacted a tree, and came to rest nose down.During a postaccident examination by a Federal Aviation Administration Inspector, the engine cowling was removed and no visual anomalies were noted with the engine. The propeller and spinner were removed; and a test run propeller and temporary fuel tank were installed. The engine was started and operated normally; slowly, the power was increased to 2,400 RPM and the oil pressure was normal. After operating for a short time, the power was decreased and the engine was shutdown. There were no anomalies noted that would have precluded normal operation.NTSB Identification: WPR16LA07914 CFR Part 91: General AviationAccident occurred Wednesday, March 02, 2016 in Fountain Hills, AZAircraft: PIPER PA 22-150, registration: N4356AInjuries: 2 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 2, 2016, about 1600 mountain standard time, a Piper PA-22-150 airplane, N4356A, executed a precautionary landing onto a sandy wash following a partial loss of engine power near Fountain Hills, Arizona. The private pilot and passenger were not injured; and the airplane sustained substantial damage to the wings. The airplane was registered to, and operated by, a private party as a 14 Code of Federal Regulations Part 91 personal flight. Visual meteorological conditions prevailed at the time of the accident, and no flight plan was filed. The local flight originated from Phoenix-Mesa Gateway Airport (IWA), Phoenix, Arizona. The pilot reported that they were flying low, about 700 feet above the ground, taking pictures of the river when the airplane's engine started to sputter. The pilot added full power and ensured that the mixture and carburetor heat were full forward. Unable to regain full power, he landed the airplane on a sandy wash. During the landing roll, the airplane sunk into the sand and the right wing impacted vegetation. The airplane nosed over and came to rest with its back against a berm. The airplane has been recovered to a secure location for further examination.

FAA Flight Standards District Office: FAA Scottsdale FSDO-07

FORT MCDOWELL, AZ - Authorities say a small plane has crashed on the Fort McDowell Reservation but there are no reported injuries.Maricopa County Sheriff's officials say the Piper Tri-Pacer plane went down Wednesday afternoon near Fort McDowell Road and State Route 87.FAA officials say the plane experienced engine trouble and the pilot was forced to land in a wash nearby.Officials say one of the wings struck a tree when it landed and the plane was badly damaged. The aircraft had departed from Falcon Field for a local flight, according to the FAA.Authorities say the two people aboard the single-engine plane are being evaluated by Fort McDowell Fire Department paramedics.Sheriff's officials say they are assisting Fort McDowell authorities in the investigation of the crash.Original article can be found here: http://www.abc15.com

PHOENIX - A small plane has crashed near Shea and the Beeline Highway on the Fort McDowell Indian Reservation.
The Federal Aviation Administration said the plane had to make an emergency landing on the road.Nobody was injured in the crash.Original article can be found here: http://www.12news.com

PHOENIX (KPHO/KTVK) - A small aircraft has reportedly gone down on the Fort McDowell Reservation.According to the Maricopa County Sheriff's Office, the Piper Tri-Pacer aircraft went down northwest of Shea Blvd. and the Beeline Hwy.No injuries are reported.It's unknown how many passengers were on board. MCSO is assisting the Fort McDowell police and fire departments in the investigation.Original article can be found here: http://www.tucsonnewsnow.com

SCOTTSDALE, Ariz. (AP) - Authorities say a small plane has crashed on the Fort McDowell Reservation but there are no reported injuries.
Maricopa County Sheriff's officials say the Piper Tri-Pacer plane went down Wednesday afternoon near the Verde River off the Beeline Highway.Authorities say the two people aboard the plane are being evaluated by Fort McDowell Fire Department paramedics.The cause of the crash is unclear at this time.Footage from television news helicopters show the plane flipped over with damage to its wings but largely intact.Sheriff's officials say they are assisting Fort McDowell authorities in the investigation of the crash.Original article can be found here: http://www.kvoa.com

While there is no for-sale sign at Google’s hangar at the Moriarty Municipal Airport, Mayor Ted Hart said he has learned it is on the market and is upset that the company isn’t working with the city on selling the 60,000-square-foot building.

The mayor of Moriarty said he is concerned about the city being left out of the loop in an effort to find a new owner of the airport hangar that was to have housed Google’s fleet of solar-powered drones.Moriarty Mayor Ted Hart said at the end of a recent council meeting that he was upset to have just learned that Google put its Titan Aerospace hangar at the Moriarty Municipal Airport on the real estate market without discussing it with any city or airport official.Last year, Google announced it had changed its mind about using the 60,000-square-foot airport hangar built at the Moriarty airport to develop an alternative method for delivering broadband, wireless Internet service using solar-powered drones. Google paid the state $995,000 to make up for a grant used to upgrade infrastructure at the airport.But Hart said the state was not the only partner in making the airport ready for Titan. Federal Aviation Administration grants were also used at the airport, he said, and FAA regulations have tight restrictions for what can be flown out of the airport.“The FAA has very specific uses that it will or won’t allow,” Hart said.Even though Google owns the large hangar, Hart said the city still owns the land it sits on and was worried if the hangar would be shown to potential buyers using standard safety and security procedures.When Google acquired Titan Aerospace in 2014, the state offered incentives to keep Titan operations at the airport where the New Mexico-based company had been testing its solar-powered drone for two years prior to the Google acquisition. Titan’s large, high-flying and lightweight drones caught the eye of Google that is competing with Facebook to provide greater Internet access using unmanned aircraft rather than orbiting satellites.Original article can be found here: http://www.abqjournal.com

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 2, 2016, about 1250 Pacific standard time, a Boeing A75N1 (PT17), N63555, touched down hard during an aborted takeoff following a loss of engine power at Palm Springs International Airport, Palm Springs, California. Palm Springs Air Museum was operating the airplane under the provisions of Title 14 Code of Federal Regulations (CFR) Part 91. The airline transport pilot sustained minor injuries and one passenger sustained serious injuries. The airplane sustained substantial damage. The local personal flight was departing. Visual meteorological conditions (VMC) prevailed, and no flight plan had been filed.The pilot reported that passing through 200 feet on the takeoff the engine lost power. He elected to abort the takeoff, and the airplane landed hard.The National Transportation Safety Board investigator-in-charge and inspectors from the Federal Aviation Administration examined the wreckage. Both of the main landing gear fractured and separated at the root, and both of the wings buckled. Portions of the bottom cylinders broke off. Fuel was drained from the gascolator, and a water paste test had no reaction indicating that water contamination was not present. There was no external evidence of catastrophic mechanical malfunction. The wreckage was removed to a recovery facility for further examination.

FAA Flight Standards District Office: FAA Riverside FSDO-21

PALM SPRINGS, Calif. - Biplane pilots are reacting to a Biplane crash landing earlier this week at the Palm Springs International Airport. The pilot has been released from the hospital and the Federal Aviation Administration is taking over the investigation.The air museum said the passenger was a participant in its plane ride program but they can't release any information on that person's condition.The vintage Stearman Biplane had engine troubles and landed hard at the airport Wednesday afternoon.Kent Thomas is a pilot for Palm Springs Biplane Rides.He's been flying airplanes since the late '70s."Airplanes, in my opinion, are a very safe way to travel, and the more training you have, the safer they are," Thomas said.Thomas said with the biplane, the landing is the hardest part."This airplane has the third wheel on the tail rather than on the nose. So when you land, this plane has a tendency to want to reverse directions quickly," Thomas said. After a quick look around, Thomas shared the secret to success."The key to flying any airplane, they say be ahead of the airplane, anticipating what's going to happen in the very near future," Thomas said.After a 10 minute flight and a smooth landing, Thomas reflected on Wednesday's crash."They were able to walk away from the crash, so actually that's a good outcome," Thomas said. Fred Bell, with the Palm Springs Air Museum, said the plane is in the hands of the FAA and the National Transportation Safety Board and it will be a while before they know what happened."We had an airplane act up, just as you would a car or something else that acted up. And we need to figure out why it did what it did. If there are corrective measures, we'll take them at that time," Bell said. While the investigation continues Bell said it's business as usual.As for Thomas, he's confident his plane will continue to be as safe as ever.Officials at the Palm Springs Air Museum said they'll continue running flights despite losing one of their aircraft.Palm Springs Biplane Rides will also continue operating as normal.Story and video: http://www.kesq.com

PALM SPRINGS, Calif. - Emergency officials responded to the Palm Springs International Airport on Wednesday after a biplane made a hard landing on the runway, injuring two people on board.Stearman aircraft biplane has extremely hard landing at Palm Springs International Airport, injuring two people on board.The extent of their injuries is unknown at this time but both were taken to the hospital as a precaution.The Palm Springs Fire Department confirmed the information to KESQ and CBS Local 2 shortly after the incident, which occurred at about 1 p.m.Officials with the Palm Springs Air Museum said the biplane was a Stearman aircraft. Spokeswoman Ann Greer said the biplane reportedly lost power for some unknown reason before making the hard landing.Palm Springs Airport Director Tom Nolan said the incident shut down airport operations for about 45 minutes. Several incoming and outgoing flights were delayed while crews worked to clear the aircraft from the runway. Runways were back open at about 2 p.m.The Federal Aviation Administration issued a statement saying the aircraft is a vintage Boeing PT 17 biplane. The tail number is N63555. The FAA and National Transportation Safety Board are investigating the incident.The FAA and NTSB don't identify people involved in aircraft incidents, officials said in the statement.Passengers on other planes were tweeting that they weren't being allowed to deplane for about a half hour in the aftermath of the incident.Original article can be found here: http://www.kesq.com

Two people were injured after an airplane crashed during an "aborted takeoff" at the Palm Springs International Airport Wednesday afternoon.Just before 1 p.m., the the biplane reached 200 feet before it lost power and returned to the runway, said Fred Bell, managing director of the Palm Springs Air Museum, which owns the airplane. The plane landed and skidded off runway."It doesn't appear anyone was seriously injured," Bell said.The Palm Springs Fire Department confirmed that two people were taken to a local hospital, but referred other questions to airport officials.According to Air Traffic Control radio transmissions, the plane crash forced all runways to shut down.Officials used a flatbed truck to remove the biplane from the runway at about 2 p.m.The single-engine plane - a 1940s-era Stearman - is registered to the Air Museum, according to Federal Aviation Records.It was donated to the museum in January 2010 by Indian Wells residents Wayne and Laura Hoffman.The FAA has been notified and the crash is under investigation.Original article can be found here: http://www.desertsun.com

Aviation officials are investigating after an antique bi-plane experiencing engine trouble and a small fire crashed at Palm Springs International Airport Wednesday afternoon, sending two people to the hospital and damaging the Stearman aircraft.The Boeing PT-17’s pilot radioed after taking off from the airport they were having engine problems and had to return, according to Federal Aviation Administration spokesman Ian Gregor.Two people were on the plane, whose tail number is N63555. They crashed while landing at about 12:50 p.m. The plane was “substantially damaged,” Gregor reported.FAA and National Transportation Safety Board officials are investigating.The two-seat bi-planes were originally used as military trainers, barnstormers and crop dusters. The 1946 Boeing PT-17 is based at the Palm Springs Air Museum, an airport tenant.The people got out of the plane on their own and were taken to the hospital, Palm Springs Deputy Fire Chief Ron Beverly said. He referred other questions to airport officials.Palm Springs Air Museum spokeswoman Ann Greer disputed that the plane crashed as reported by the FAA.“The plane had a hard landing,” Greer said. “It lost power.”Airport Director Tom Nolan said he had no information about who was in the plane or the extent of possible injuries. The plane was “a little bumped up” but fully intact. Nolan didn’t know if the wheels were down during landing in the airport’s peak season.The plane had a “disruption in power” and a small fire coming from the engine compartment as it landed “quite hard” on the runway, he said.Greer couldn’t provide the pilots’ names. She didn’t know if they were staff or volunteers or if they were injured.A crane lifted the plane onto a flatbed truck and the runway was cleared within 50 minutes, Nolan said.

CHESTER CHARTER INC: http://registry.faa.gov/N94569NTSB Identification: ERA16LA12214 CFR Part 91: General AviationAccident occurred Tuesday, March 01, 2016 in Chester, CTProbable Cause Approval Date: 05/01/2017Aircraft: CESSNA 152, registration: N94569Injuries: 1 Uninjured.NTSB investigators may not have traveled in support of this investigation and used data provided by various sources to prepare this aircraft accident report.The private pilot completed a prerental checkout in the airplane and then departed for a local flight. Upon return to the airport, the pilot landed the airplane beyond the midpoint of the 2,722-ft-long runway, and the airplane then veered off the right side of the runway and impacted a fence. The pilot reported no anomalies with the brakes to the operator during his prerental checkout in the airplane. However, after the accident, he reported that one of the brakes felt “spongy” during the landing attempt. Postaccident examination of the brakes revealed no evidence of any anomalies that would have precluded normal operation.The National Transportation Safety Board determines the probable cause(s) of this accident as follows:The pilot’s failure to maintain directional control of the airplane during the landing, which resulted in a runway excursion.On March 1, 2016, about 1130 eastern standard time, a Cessna 152, N94569, was substantially damaged during a runway excursion after landing at the Chester Airport (SNC), Chester, Connecticut. The private pilot was not injured. Visual meteorological conditions prevailed and no flight plan was filed for the local flight conducted under the provisions of 14 Code of Federal Regulations Part 91. According to a Federal Aviation Administration (FAA) inspector, the airplane landed on runway 35, a dry, 2,722-foot-long, 50-foot-wide, asphalt runway. After landing, the airplane continued off the right side on the runway, through a fence, and came to rest in the grassy area. According to witnesses, the airplane touched down about 200 feet beyond the midpoint of the runway. In a written statement the pilot stated that during rollout the right brake felt "ok", but the left brake felt "spongy", and that the airplane failed to stop before it departed the right side of the runway. According to a flight instructor for the operator, he and the pilot flew together for approximately two hours on both the day before and the day of the accident to complete a pre-rental checkout for the pilot in the accident airplane. At no time did the pilot mention anomalies or malfunctions of the airplane's braking system.Postaccident examination of the airplane by an FAA inspector and an airframe and powerplant mechanic revealed substantial damage to the engine firewall. Functional testing of the brakes showed that they were operational and did not reveal evidence any pre- or post-impact mechanical anomalies. A detailed examination of the brake revealed that there were no signs of hydraulic fluid or damage to the brake lines, and the brake pucks were nominal in size with no abnormal wear. The airplane was equipped with a Lycoming O-235 series, 108-horsepower engine. The airplane had been operated for about 100 hours since its most recent annual inspection, which was performed on September 1, 2015.The pilot reported 1,300 hours of total flight experience, of which 75 hours were in the accident airplane make and model.

NTSB Identification: ERA16LA122 14 CFR Part 91: General AviationAccident occurred Tuesday, March 01, 2016 in Chester, CTAircraft: CESSNA 152, registration: N94569Injuries: 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 1, 2016, about 1130 eastern standard time, a Cessna 152, N94569, was substantially damaged during a runway excursion after landing at the Chester Airport (SNC), Chester, Connecticut. The private pilot was not injured. Visual meteorological conditions prevailed and no flight plan was filed for the local flight conducted under the provisions of 14 Code of Federal Regulations Part 91.According to a Federal Aviation Administration (FAA) inspector, after flying .7 hours with a flight instructor, the pilot elected to do a local area solo flight. During this solo flight the pilot landed on runway 35, a dry, 2,722-foot-long, 50-foot-wide, asphalt runway. After landing, the airplane continued off the right side on the runway, through a fence, and came to rest in the grassy area. According to witnesses, the airplane touched down about 200 feet beyond the midpoint of the runway.Postaccident examination of the airplane by an FAA inspector and an airframe and powerplant mechanic revealed damage to the engine mount, the right side nose landing gear rod, and the propeller. Functional testing of the brakes showed that they were operational and did not reveal evidence any pre- or post-impact mechanical anomalies.Weather reported at SNC at the time of the accident included sky clear, 10 miles of visibility and wind 350 degrees at 8 knots.