Wednesday, March 01, 2017

Bellanca 17-30A Super Viking, N39894: Accident occurred March 01, 2017 near Carson Airport (KCXP), Carson City, Nevada

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

Additional Participating Entities:

Federal Aviation Administration / Flight Standards District Office: Reno, Nevada
Continental Motors; Mobile, Alabama

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

http://registry.faa.gov/N39894


Location: Carson City, NV

Accident Number: WPR17LA072
Date & Time: 03/01/2017, 1250 PST
Registration: N39894
Aircraft: BELLANCA 17-30A
Aircraft Damage: Substantial
Defining Event: Fuel related
Injuries: 1 Serious
Flight Conducted Under: Part 91: General Aviation - Personal

Analysis 

The airline transport pilot was conducting the airplane's first flight after about 1 1/2 years of inactivity and the completion of an annual inspection. A witness reported that the airplane took off normally, but the retractable landing gear remained extended. As the airplane neared the end of the runway, about 300 ft above ground level, the engine sounded as though it "decreased to idle." The airplane entered a right, 180o turn and descended rapidly before impacting the ground.

During a postaccident test run, the engine operated normally at both idle and full power settings and during abrupt changes between idle and full power. However, it operated inconsistently at 2,100 rpm for about 30 seconds before stabilizing at that power setting. During this time, the fuel pump pressure fluctuated. Following the test run, the fuel manifold valve was disassembled, revealing rust on the screen, lower housing, and plunger, consistent with exposure to water. The diaphragm was removed and a small amount of fuel was found on the "dry" side of the valve; the vent extending from this section was examined and clear of debris. Examination of the airframe and engine maintenance logs revealed that the airplane flew a total of 73 hours and underwent 3 annual inspections in the previous 8 years. It is likely that water accumulated in the fuel system sometime during the airplane's prolonged periods of disuse, resulting in corrosion of the fuel manifold valve's internal components. Because the corrosion was internal, it would not have been detected without disassembly of the fuel manifold, which is not part of the annual inspection procedure. It is likely that this corrosion caused the manifold valve plunger to temporarily stick, which restricted fuel flow to the engine and resulted in the anomalous operation during the postaccident test run as well as the loss of power on the accident flight. Following the loss of engine power, the pilot initiated a turn back to the runway, during which the airplane exceeded its critical angle of attack and experienced an aerodynamic stall.

Probable Cause and Findings

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

A total loss of engine power due to internal corrosion of the fuel manifold valve. Also causal was the pilot's decision to return to the runway following the loss of engine power shortly after takeoff, and his exceedance of the airplane's critical angle of attack during the turn, which resulted in an aerodynamic stall. 

Findings

Aircraft

Fuel distribution - Fatigue/wear/corrosion (Cause)
Fuel distribution - Malfunction (Cause)

Personnel issues
Aircraft control - Pilot (Cause)

Factual Information 


On March 1, 2017, about 1250 Pacific standard time, a Bellanca 17-30A, N39894, experienced a loss of engine power shortly after takeoff from the Carson Airport (CXP), Carson City, Nevada. The pilot, sole occupant, was seriously injured, and the airplane sustained substantial damage to both wings. The airplane was registered to and operated by the pilot as a 14 Code of Federal Regulations Part 91 personal flight. Visual meteorological conditions prevailed at the time of the accident no flight plan was filed for the local flight.

At the time of this report, the pilot was unable to provide a statement or complete the NTSB Pilot/Operator Aircraft Accident/Incident Report Form 6120.1.

A witness reported that he observed the airplane takeoff normally, with the exception that the landing gear remained in the down position. At the end of the runway, when the airplane was no higher than 300 feet, it sounded as if the engine decreased to idle. The airplane made a right 180o turn and descended rapidly before impacting the ground.

Postaccident examination of the airframe revealed continuous control continuity throughout the airframe. In addition, control continuity was established from the cabin to the throttle, mixture, and propeller controls. The fuel lines were intact from the engine to the firewall, and from the wing tanks to the fuselage; the remaining lines were inaccessible due to airframe damage. Air was blown from the engine driven fuel pump inlet line aft through the fuel selector and air/fuel exited the left wing fuel tank outlet line. With no obvious anomalies with the airframe or engine, the engine was shipped to Continental Motors to be run in a test cell.

The engine was installed into a test cell. It started normally and ran for a while at 1,200 RPM with no anomalies noted. The power was increased to 2,100 rpm and the engine operated inconsistently; the fuel pump pressure was fluctuating, and after about 30 seconds the engine stabilized. After stabilization, a magneto check was completed and no abnormalities were noted. The engine power was increased to 2,400 RPM momentarily before full power was applied; the engine continued to operate normally. The engine power was abruptly changed between idle and full power several times with no anomalies noted. Unable to recreate the inconsistent running engine, it was shut down normally and removed from the test cell.

The fuel components were removed from the engine. The fuel manifold valve was disassembled and rust indicative of corrosion was present on the screen and lower housing of the unit. The plunger was removed and it also exhibited rust. The diaphragm was removed and a small amount of fuel was found on the "dry" side of the valve; the vent extending from this section was examined and clear of debris.

The most recent entries from the airplane's airframe and engine maintenance logbooks were three annual inspections that occurred over a span of about 8 years. The tach time difference between these inspections was a total of 73 hours, for an average of 9 hours a year. The wife of the pilot reported that they purchased the airplane in 2002, and it has been parked in a hangar for a majority of their ownership. About 1.5 years leading up to the accident, the airplane had been undergoing an annual inspection and new paint, which was completed on February 24, 2017. When the maintenance was completed, the pilot ran the airplane's engine on the ground for about 45 minutes with no anomalies noted; the accident flight was the first flight post maintenance.

According to a Continental Motors representative the fuel manifold valve is generally not disassembled by a mechanic in the field, and there are rarely issues with this engine component. If fuel issues are suspected, the troubleshooting section of the Continental Motors Standard Practices Manual (M-0) directs the mechanic to an isolated fix. If the problem is isolated to the fuel manifold, it is to be removed and either sent to an appropriate overhaul facility, or replaced by a new or rebuild from Continental Motors. 

History of Flight

Initial climb

Fuel related (Defining event)
Loss of engine power (total)
Off-field or emergency landing

Landing
Aerodynamic stall/spin
Collision with terr/obj (non-CFIT) 

Pilot Information

Certificate: Airline Transport; Flight Engineer
Age: 61, Male
Airplane Rating(s): Multi-engine Land; Multi-engine Sea; Single-engine Land; Single-engine Sea
Seat Occupied: Left
Other Aircraft Rating(s): Glider
Restraint Used: 3-point
Instrument Rating(s): Airplane
Second Pilot Present: No
Instructor Rating(s): None
Toxicology Performed: No
Medical Certification: Class 1 Without Waivers/Limitations
Last FAA Medical Exam: 10/28/2016
Occupational Pilot: Yes
Last Flight Review or Equivalent:
Flight Time: 22000 hours (Total, all aircraft) 

Aircraft and Owner/Operator Information

Aircraft Manufacturer: BELLANCA
Registration: N39894
Model/Series: 17-30A
Aircraft Category: Airplane
Year of Manufacture: 1973
Amateur Built: No
Airworthiness Certificate: Normal
Serial Number: 73-30544
Landing Gear Type: Tricycle
Seats: 4
Date/Type of Last Inspection: 02/24/2017, Annual
Certified Max Gross Wt.: 
Time Since Last Inspection: 1 Hours
Engines: 1 Reciprocating
Airframe Total Time: 3394 Hours as of last inspection
Engine Manufacturer: CONT MOTOR
ELT: Not installed
Engine Model/Series: IO 520 SERIES
Registered Owner: On file
Rated Power: 285 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: CXP, 4705 ft msl
Observation Time: 1255 PST
Distance from Accident Site: 0 Nautical Miles
Direction from Accident Site:
Lowest Cloud Condition: Clear
Temperature/Dew Point: 7°C / -9°C
Lowest Ceiling: None
Visibility: 10 Miles
Wind Speed/Gusts, Direction: 4 knots, 100°
Visibility (RVR):
Altimeter Setting: 30.41 inches Hg
Visibility (RVV):
Precipitation and Obscuration: No Obscuration; No Precipitation
Departure Point: Carson City, NV (CXP)
Type of Flight Plan Filed: None
Destination: Carson City, NV (CXP)
Type of Clearance: None
Departure Time: 1250 PST
Type of Airspace:

Airport Information


Airport: Carson Airport (CXP)
Runway Surface Type: Asphalt
Airport Elevation: 4705 ft
Runway Surface Condition: Dry
Runway Used: 9
IFR Approach: None
Runway Length/Width: 6100 ft / 75 ft
VFR Approach/Landing: Forced Landing 

Wreckage and Impact Information

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

NTSB Identification: WPR17LA072
14 CFR Part 91: General Aviation
Accident occurred Wednesday, March 01, 2017 in Carson City, NV
Aircraft: BELLANCA 17-30A, registration: N39894
Injuries: 1 Serious.

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, 2017, about 1250 Pacific standard time, a Bellanca 17-30A, N39894, experienced a loss of engine power shortly after takeoff from the Carson Airport (CXP), Carson City, Nevada. The pilot, sole occupant, was seriously injured, and the airplane sustained substantial damage to both wings. The airplane was registered to, and operated by, the pilot as a 14 Code of Federal Regulations Part 91 personal flight. Visual meteorological conditions prevailed at the time of the accident and it is unknown if a flight plan was filed. The flight was destined for an unknown location.

A witness reported that they observed the airplane takeoff normally, with the exception that the landing gear remained in the down position. At the end of the runway, when the airplane was no higher than 300 feet, it sounded as if the engine decreased to idle. The airplane made a right 180 degree turn and descended rapidly before impacting the ground. 

The airplane has been recovered to a secure location for further examination.



Carson City Sheriff’s Office says there was a plane crash at the Carson City Airport on Wednesday afternoon. 

Officials say a small plane was in the ditch on the north side of the runway.

According to the Nevada Appeal, the plane was a 1973 Bellanca registered out of Kingman, Arizona and that the pilot was taken to the hospital with non-life threatening injuries. 

Story and video:  http://www.ktvn.com





CARSON CITY, Nev. (KOLO) - The pilot of a small plane was flown to Renown Regional Medical Center Wednesday after his plane went down in Carson City.

Sheriff Ken Furlong says it happened about 12:50PM March 1, 2017. The pilot, a Carson resident, had just taken off from the Carson airport but turned around and crashed at the north side of the airport. He was the only person on board.

No status about his condition has been released, but Furlong says he was conscious when he was taken to Renown.

There is no word yet regarding why he turned around or what led to the Viking 2-seater to crash.

The airport was temporarily closed during investigation and cleanup, but has since reopened.

Story and video:  http://www.kolotv.com







CARSON CITY, Nev. (News 4 & Fox 11) — The Carson City Sheriff's Office has confirmed a small plane crash at the Carson City airport.

According to Sheriff Ken Furlong, the pilot of the plane was unconscious and is being transported to Reno via CareFlight.

The crash was reported around 12:50 p.m.

Officials say the perimeter is being secured and the airport is closed.

No one else was on board at the time of the crash.

Source:   http://mynews4.com

Carson City Sheriff's Office 
Subject: Airport Temporarily Closed
Date: March 1, 2017
Time: 1:45 p.m.

(Carson City, NV) The Carson City Airport is temporarily closed until further notice. At about 12:50 p.m. dispatch was notified of a possible aircraft crash on the north side of the airport. According to Sheriff Ken Furlong the aircraft was identified as a local aircraft. At the time of the crash the aircraft had one occupant. The extent of the occupant’s injuries are unknown at this time. He has been Care Flighted to Renown for treatment.

Maule MX-7-180A, RJ Properties Inc., N600XX: Accident occurred March 01, 2017 in Live Oak, Sutter County, California

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

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

NTSB Identification: GAA17CA168
14 CFR Part 91: General Aviation
Accident occurred Wednesday, March 01, 2017 in Live Oak, CA
Probable Cause Approval Date: 04/10/2017
Aircraft: MAULE MX7, registration: N600XX
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, while on base for his private grass airstrip, he noticed he was high, so he added flaps to increase his descent. He added that, on final, the airspeed was a little fast and during the landing, he flared the airplane “a little high.” After touchdown, the pilot applied the brakes, but the airplane did not respond, so he applied “a little more brake”; subsequently, the airplane nosed over and came to rest inverted.
The airplane sustained substantial damage to both wings and the empennage.

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

The pilot reported as a safety recommendation that he should have performed a go-around instead of attempting to “salvage the landing.”

The National Transportation Safety Board determines the probable cause(s) of this accident as follows:
The pilot’s failure to maintain a stabilized approach and his subsequent incorrect brake application during the landing roll, which resulted in a nose-over.

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

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

RJ Properties Inc: http://registry.faa.gov/N600XX 

NTSB Identification: GAA17CA168

14 CFR Part 91: General Aviation
Accident occurred Wednesday, March 01, 2017 in Live Oak, CA
Aircraft: MAULE MX7, registration: N600XX
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 while on base for his private grass airstrip, he noticed he was high, so he added flaps to increase his descent. He reported that on final the airspeed was a little fast and during the landing, he flared the airplane "a little high". The pilot further reported that after touchdown, he applied the brakes, but the airplane did not respond, so he applied "a little more brake"; subsequently, the airplane nosed over and came to rest inverted.

The airplane sustained substantial damage to both wings and the empennage.

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

The pilot reported as a safety recommendation that he should have performed a go-around instead of attempting to "salvage the landing".



LIVE OAK, Calif.  —   A man was injured Wednesday afternoon after his plane crashed in Sutter County, officials said.

The pilot suffered minor to moderate injuries and drove himself to the hospital, the Sutter County Fire Department said.

The single-engine plane crash around 3:45 p.m. near Live Oak.

The fire department said the pilot was landing on a grass landing strip near Pennington and Hedger roads when the plane flipped over.

The pilot was the only person on board.

No other details were released. 

Source:  http://www.kcra.com

Spring Training: CAL FIRE Air Tankers Exercise over Nevada and Placer Counties



NEVADA CITY, Calif. March 1, 2017 –  Airtankers used by CAL FIRE to fight wildfires are currently training in the airspace over Nevada and Placer Counties. The training will continue for the next few days. The tankers and their pilots use the regularly scheduled “spring training” to get back into fighting shape. The Grass Valley air attack base is home to two ST2 tankers, two spotter planes and one helicopter. During the winter season, all air tankers are stationed at Sacramento’s McClellan base.

In 2016, year five of the drought, CAL FIRE and the Forest Service brought additional resources on earlier than ever to fight any new starts. Traditionally, CAL FIRE’s air tankers make their way from McClellan to Grass Valley in June.



The Grass Valley Emergency Command Center processes an average of 24,000 calls yearly and is jointly run by CAL FIRE and the Forest Service. Throughout the fire season, the Forest Service staffs the ECC from 7:00 am-7:00 pm and CAL FIRE dispatch center is operated 24 hrs a day. The joint ECC is staffed by 10 dispatchers, daily, during the fire season.

From late April through October, 4 pilots, 2 air attack officers, and additional staff are daily on duty for initial attack at the GV Air Attack Base representing both CAL FIRE and the Forest Service. There are two assigned CAL FIRE tankers, 1 CAL FIRE air attack plane, 1 Forest Service air attack plane and the Forest Service Bell 407 helicopter, complete with the Helitack crew.

Source:  https://yubanet.com

Cessna 172S Skyhawk, St. Pete Air, N22904: Accident occurred March 01, 2017 at Albert Whitted Airport (KSPG), St. Petersburg, Pinellas County, Florida

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

Additional Participating Entity:
Federal Aviation Administration / Flight Standards District Office: Tampa, Florida

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

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

V L Aviation LLC: http://registry.faa.gov/N22904


NTSB Identification: GAA17CA163
14 CFR Part 91: General Aviation
Accident occurred Wednesday, March 01, 2017 in St Petersburg, FL
Probable Cause Approval Date: 09/22/2017
Aircraft: CESSNA 172S, registration: N22904
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 solo flight, he was performing takeoffs and full-stop landings in the traffic pattern. During the landing roll, he configured the flaps to 0 and applied full power. The airplane pulled to the left, and he overcompensated the right rudder pedal application. “In an immediate reaction to reverse this I applied left rudder to quickly and went immediately to far left causing a fishtailing effect.” The airplane exited the runway to the left and struck runway signage and a fence. The airplane sustained substantial damage to the left wing, the landing gear attachment points, the horizontal stabilizer, and the elevator.

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

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

The student pilot’s overcompensation of right rudder pedal application during the landing roll, which resulted in a loss of directional control and impact with runway signage and a fence. 

NTSB Identification: GAA17CA163
14 CFR Part 91: General Aviation
Accident occurred Wednesday, March 01, 2017 in St Petersburg, FL
Aircraft: CESSNA 172S, registration: N22904
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 solo flight he was performing takeoffs and full stop landings in the traffic pattern. During the landing roll, he configured the flaps to zero and applied full power. The airplane pulled to the left and he overcompensated the right rudder pedal application. "In an immediate reaction to reverse this I applied left rudder to quickly and went immediately to far left causing a fishtailing effect." The airplane exited the runway to the left and struck runway signage and a fence. The airplane sustained substantial damage to the left wing, the landing gear attachment points, the horizontal stabilizer and the elevator.

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





ST. PETERSBURG — A student pilot escaped injury Wednesday morning when his small plane crashed while attempting a landing at Albert Whitted Airport, according to St. Petersburg police.

The male pilot was practicing takeoffs and landings, according to police, when he crashed in front of the airport tower while attempting a landing around 11:20 a.m.

The pilot was alone on the plane and was not injured, fire officials said. "Pilot error" led to the crash, according to St. Petersburg police, but the agency declined to identify the pilot.

The Cessna 172S Skyhawk ran off the side of Runway 7 and struck a fence after landing, said Federal Aviation Administration spokeswoman Kathleen Bergen.

She said the FAA is investigating the crash to determine whether any regulations were violated, although that process could take months. The National Transportation Safety Board will determine what led to the crash, Bergen said.

Fire officials said the crash damaged the plane's landing gear and caused a minor fuel leak.

Airport manager Richard Lesniak said the student pilot was taking lessons with St. Pete Air. Company officials declined to return calls for comment.

The fixed wing single-engine plane, which was manufactured in 2005, is registered to VL Aviation LLC in Snell Isle.

Source:  http://www.tampabay.com







ST. PETERSBURG, Fla. - A small plane crashed in front of the airport tower at Albert Whitted Airport Wednesday morning.

The airport is located at 107 8th Avenue SE in St. Petersburg.

When the fire department arrived on scene they found a Cessna 172S Skyhawk that had crashed in front of the tower, primarily damaging the landing gear. Police say the pilot was a student that was practicing takeoffs and landings and while attempting to land, the plane crashed near the tower. 

The male pilot was the only occupant on board the aircraft at the time of the crash. No injuries were reported. 

Fire officials handled a minor fuel leak. The FAA was notified of the crash and will complete the investigation. 

Story and video:  http://www.abcactionnews.com

Transportation Security Administration documents reveal security lapses at Stewart International Airport (KSWF)



NEW YORK — Sensitive documents leaked after a data exposure at an upstate New York airport have revealed several major security lapses in recent years.

Dozens of files seen by ZDNet list a catalog of security failings over the past few years at Stewart International Airport, about 60 miles north of Manhattan, which serves hundreds of thousands of passengers each year, including high-profile guests and private charter flights.

The cache build up a unique picture of insider threats, breaches, and lapses that acknowledge the difficulty in keeping airside security to a high standard, even at smaller airports.

In one such instance, documents seen by ZDNet show how airport staff was for an unknown period in 2010 unable to screen names against the U.S. government’s watchlist of suspected terrorists who were forbidden from flying in its airspace.

A response letter by the airport manager confirmed that the airport “did not have access to the list,” and therefore badge-holding staff at the airport were not being screened properly.

The airport had to enlist the help of neighboring Westchester County Airport to carry out the checks, the letter added.

ZDNet

The government’s “no-fly” list currently prevents around 47,000 passengers from flying within, into, or out of U.S. airspace, according to leaked documents, a figure that rocketed during the Obama administration.

But the list has proven controversial, not least because it’s shrouded in secrecy. Only a select few people who have challenged their membership are even aware that they have been on the list, which includes regular citizens, diplomats and politicians. CBS News obtained a copy of the no-fly list in 2006, which showed that the list was riddled with mistaken identities, wrongly added names, and even dead people.

It’s not clear what led to the screening mishap, but emails found in the cache of exposed file show one security-cleared employee of AVPorts, a third-party operations provider that manages the airport, regularly downloaded the no-fly list from a secure Homeland Security portal.

A former head of the Transportation Security Administration (TSA) explained that both passengers and airport staff are checked against the no-fly list centrally, making it more difficult to slip through the cracks.

“All airline passengers are screened for the no-fly list automatically by TSA centrally when a flight reservation is made,” said Kip Hawley, who helped to found the agency following the September 11 attacks. “It looks like the airport is supposed to screen badge-holders against the no-fly list, and maybe they weren’t doing that so they got the notice of violation,” he said.

But Hawley said that the so-called “insider threat” remains a concern.

One email seen by ZDNet showed that the airport was concerned about the issue following an arrest of a Long Island, New York resident, which resulted in the discovery of a counterfeit badge for LaGuardia Airport. The email said that had staff not properly checked the badge, it may have allowed an uncleared person to enter the airport’s secure area.

“Please keep in mind that this could happen at any airport and we must be vigilant,” read the email sent by a senior security official at Stewart Airport.

Federal agencies continue to put greater scrutiny on the security protocols and policies of smaller airports, including Stewart, in light of the threat posed by the so-called Islamic State, or ISIS.

Among the concerns are that potential fighters who try to join the terror group on the ground in Syria and Iraq may aim to travel through smaller, regional airports in order to avoid detection by the authorities.

One field intelligence note found among the exposed files, published by Homeland Security in April 2016, said terrorists “may continue to choose smaller airports… as preferred, more attractive departure points for foreign fighter travel,” because security is perceived to be not as strict as at larger international airports.

That makes the risks greater and the need to ensure tight security controls all the more important.

A review of various letters of investigation received by the airport over the past decade point to as many as 15 separate investigations carried out by the TSA each year as a result of security lapses at the airport.

TSA inspectors wrote in one letter of investigation in 2010 that card readers installed in the airport’s corporate transit zone allowed direct access to the Air Operations Area, a highly restricted area of the airside tarmac where aircraft depart, arrive, and maneuver.

Another letter of investigation from 2011 found an unsecured baggage carousel key, which provides direct access to the airport’s secure area. The key was lent by a member of one airline’s staff to another, but it was later left on a ticket counter when the borrower returned the key.

And, a letter of investigation from mid-2012 detailed a list of multiple claimed violations, including unsupervised and unescorted access to non-cleared contractors and visitors to highly sensitive and restricted parts of the airport, known as Security Identification Display Areas.

But a concerted effort by the airport to improve security over the past three years has paid off.

One email sent by the airport’s security manager earlier last year confirmed that the TSA had not sent any letters of investigation during 2015.

Also, a comprehensive security review by TSA inspectors in the same year concluded with no findings of concern, the email said.

In a statement provided to CBS News, the TSA said:

“The documents we’ve seen referenced appear to be copies of old inspection reports that demonstrate that TSA has been performing our mission of security oversight at the airport. When we find issues that need to be addressed we point them out and work with the airport to get them resolved.”

The Port Authority of New York & New Jersey, which operates the area’s transportation facilities, including Stewart International Airport, said in a statement that its network “has not been compromised” and that issues identified several years ago have been addressed:

“Based on our investigation, the Port Authority network has not been compromised and remains sound. AVPorts, an independent contractor that handles various airport functions including serving as security manager at Stewart International Airport, maintains a separate system for administering those responsibilities. Our investigation into AVPorts separate system is ongoing.  The TSA findings in the documents in that system from several years ago were addressed at that time to the satisfaction of the TSA and are no longer relevant.”

This article originally appeared on ZDNet.com.

Source:  http://www.wdef.com




NEW YORK (FOX 5 NEWS) - Stewart International Airport in Orange County, New York, is a fairly small airport with a big problem.

Chris Vickery is a data security expert in California. Part of his job is to find private information exposed to the public and then let the companies or agencies know about their security lapse. That is exactly what he did with Stewart International Airport earlier this month. 

"I found that what's known as the remote synchronization service at this IP address was open and exposed to the entire world," Vickery said. "Anybody with an Internet connection could have downloaded from it."

Chris was then shocked to see the documents he easily downloaded from the server: tons of information about Stewart International Airport.

"When I opened it, it contained all sorts of airport data," Vickery said. "It had folders named 'HR,' 'Payroll.' It had employees' Social Security numbers as well as 107 gigabytes of email correspondence."

Chris says he immediately called the airport management company and then the Port Authority, which owns the airport. He let them know about the dangerous security breach. Several hours later, the public server shut down.

In a statement, the Port Authority said: "Based on our investigation, the Port Authority network has not been compromised and remains sound. AVPorts, an independent contractor that handles various airport functions including serving as security manager at Stewart International Airport, maintains a separate system for administering those responsibilities. Our investigation into AVPorts separate system is ongoing."

We also reached out to the TSA, which said it takes these allegations very seriously and is reviewing the incident. 

Story and video:  http://www.fox5ny.com

XtremeAir XA42, N342AW: Accident occurred March 01, 2017 at North Palm Beach County Airport (F45), West Palm Beach, Florida

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

Additional Participating Entity: 

Federal Aviation Administration / Flight Standards District Office; Miramar, Florida 

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

Location: West Palm Beach, FL
Accident Number: ERA17LA122
Date & Time: 03/01/2017, 1315 EST
Registration: N342AW
Aircraft: XTREMEAIR GMBH XA42
Aircraft Damage: Substantial
Defining Event: Loss of engine power (total)
Injuries: 1 None
Flight Conducted Under:  Part 91: General Aviation - Personal 

On March 1, 2017, about 1315 eastern standard time, an Xtremeair GMBH XA42, N342AW, was substantially damaged during a forced landing after takeoff from North Palm Beach County General Aviation Airport (F45), West Palm Beach, Florida. The airline transport pilot was not injured. Visual meteorological conditions prevailed, and no flight plan was filed for the personal flight that was operated under the provisions of 14 Code of Federal Regulations Part 91.

According to the pilot, he washed the airplane the day prior to the accident. The accident flight was the first flight of the day, and it had 22 gallons of fuel on board. During takeoff, when the airplane was approximately 150 feet above ground level, the "engine suddenly quit as if the mixture went to idle cutoff." The pilot attempted to restart the engine without success and elected to land the airplane straight ahead in a field. During the landing, the airplane touched down on soft terrain and skidded about 60 feet prior to coming to rest in the upright position. The pilot then egressed from the airplane.

According to Federal Aviation Administration (FAA) records, the two-place, conventional gear, low-wing airplane was manufactured in 2015, and was registered to the pilot at that time. It was powered by a Lycoming AEIO-580 series, 315-horsepower engine. According to the engine maintenance logbook, the most recent condition inspection was completed February 28, 2017, at a total time of 321.5 hours, and "was found to be in a condition for safe flight."

Examination of the airplane by an FAA inspector revealed that the firewall and engine mounts were substantially damaged during the forced landing. Furthermore, all three propeller blade tips were impact damaged.

An examination of the engine revealed that crankshaft continuity was confirmed to the accessory section of the engine. Oil was noted throughout the engine. During the accident sequence, dirt and sand filled the fuel injection servo. The fuel injection servo was removed, disassembled, and fuel was noted in the throttle body. There was no debris in the fuel screen. The spark plugs were removed, and corrosion was noted on them. In addition, they were all light grey in color and exhibited normal wear when compared to the Champion Check-a-Plug chart. The fuel manifold was disassembled, and no fuel was noted inside. The diaphragm was intact, and no anomalies were noted. The engine driven fuel pump was removed and could be rotated by hand. Throughout the examination no water was noted in the engine. Furthermore, the engine had no mechanical failures or anomalies that would have precluded normal operation prior to the accident.

When asked what the pilot thought happened, he stated that he had washed the airplane the day prior to the accident flight, and water might have entered the air intake and fuel injection servo on the engine. Subsequently, the water entered into the fuel system, and "resulted in the loss of power on takeoff."

Pilot Information

Certificate: Airline Transport; Flight Instructor
Age: 41, Male
Airplane Rating(s): Multi-engine Land; Single-engine Land
Seat Occupied: Rear
Other Aircraft Rating(s): None
Restraint Used: 5-point
Instrument Rating(s): Airplane
Second Pilot Present: No
Instructor Rating(s): Airplane Multi-engine; Airplane Single-engine
Toxicology Performed: No
Medical Certification: Class 1 Without Waivers/Limitations
Last FAA Medical Exam: 11/01/2016
Occupational Pilot: Yes
Last Flight Review or Equivalent: 06/06/2017
Flight Time:  11805 hours (Total, all aircraft), 220 hours (Total, this make and model), 6700 hours (Pilot In Command, all aircraft), 180 hours (Last 90 days, all aircraft), 60 hours (Last 30 days, all aircraft) 

Aircraft and Owner/Operator Information

Aircraft Make: XTREMEAIR GMBH
Registration: N342AW
Model/Series: XA42 NO SERIES
Aircraft Category: Airplane
Year of Manufacture: 2010
Amateur Built: No
Airworthiness Certificate: Experimental
Serial Number: 102
Landing Gear Type: Tailwheel
Seats: 2
Date/Type of Last Inspection: 02/28/2017, Annual
Certified Max Gross Wt.: 2200 lbs
Time Since Last Inspection:
Engines: 1 Reciprocating
Airframe Total Time: 280 Hours at time of accident
Engine Manufacturer: Lycoming
ELT: Installed, not activated
Engine Model/Series: AEIO-580-B1A
Registered Owner: On file
Rated Power: 315 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: PBI, 21 ft msl
Distance from Accident Site: 12 Nautical Miles
Observation Time: 1312 EST
Direction from Accident Site: 143°
Lowest Cloud Condition: Thin Broken / 2600 ft agl
Visibility:   10 Miles
Lowest Ceiling: Broken / 2600 ft agl
Visibility (RVR):
Wind Speed/Gusts: 10 knots /
Turbulence Type Forecast/Actual: /
Wind Direction: 110°
Turbulence Severity Forecast/Actual: /
Altimeter Setting: 30.12 inches Hg
Temperature/Dew Point: 27°C / 19°C
Precipitation and Obscuration: No Obscuration; No Precipitation
Departure Point: West Palm Beach, FL (F45)
Type of Flight Plan Filed: None
Destination: West Palm Beach, FL (F45)
Type of Clearance: None
Departure Time: 1315 EST
Type of Airspace: Class G

Airport Information

Airport: NORTH PALM BEACH COUNTY GENERA (F45)
Runway Surface Type: Grass/turf
Airport Elevation: 22 ft
Runway Surface Condition: Dry; Vegetation
Runway Used: 08L
IFR Approach: None
Runway Length/Width: 3679 ft / 75 ft
VFR Approach/Landing: Forced Landing 

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:  26.842778, -80.231667 (est)

NTSB Identification: ERA17LA122
14 CFR Part 91: General Aviation
Accident occurred Wednesday, March 01, 2017 in West Palm Beach, FL
Aircraft: XTREMEAIR GMBH XA42, registration: N342AW
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 1, 2017, about 1315 eastern standard time, an Xtremeair GMBH XA42, N342AW, was substantially damaged during a forced landing after takeoff from North Palm Beach County General Aviation Airport (F45), West Palm Beach, Florida. The airline transport pilot was not injured. Visual meteorological conditions prevailed, and no flight plan was filed for the personal flight that was operated under the provisions of 14 Code of Federal Regulations Part 91.

According to the pilot, the accident flight was the first flight of the day, and the airplane had about 20 gallons of fuel on board. During takeoff, when the airplane was approximately 150 feet above ground level, the "engine suddenly quit as if the mixture went to idle cutoff." The pilot attempted to restart the engine without success and elected to land the airplane straight ahead in a field. During the landing, the airplane touched down on soft terrain and skidded about 60 feet prior to coming to rest in the upright position. The pilot then egressed from the airplane.

According to Federal Aviation Administration (FAA) records, the two-place, conventional gear, low-wing airplane was manufactured in 2015, and was registered to the pilot at that time. It was powered by a Lycoming AEIO-580 series, 315-horsepower engine. According to a photograph, the engine oil filter exhibited a date of February 28, 2017, and a time of 321.5 hours.

Examination of the airplane by an FAA inspector revealed that the firewall and engine mounts were substantially damaged during the forced landing. Furthermore, all three propeller blade tips were impact damaged.

The engine was retained for further examination.


PALM BEACH GARDENS, Fla. (CBS12) — An XtremeAir XA42 slid off the runway and came to rest in a marsh at the North Palm Beach County Airport, the FAA said Wednesday.

The incident happened just after 1 p.m. and drew multiple rescue crews from Palm Beach County Fire Rescue and Palm Beach Gardens Fire Rescue.

According to Palm Beach County Fire Rescue, one aircraft is 75 yards out in a swampy area and there are no reported injuries.

The FAA said the pilot was the only one on board.

The Palm Beach County Sheriff's Office is on scene, assisting with the investigation.

Fire Rescue reported the incident involved two aircraft. It's unclear at this moment how the second aircraft was involved.

Source:   http://cbs12.com






PALM BEACH COUNTY, Fla. -- Palm Beach County Fire Rescue crews are investigating a plane accident at North Palm Beach County Airport.

Two aircraft were involved in the incident, according to Palm Beach County Fire Rescue.

Officials with the FAA say an XtremeAir XA42 aircraft slid off the grass runway and came to rest approximately 75 yards into a marsh area. No injuries were reported. Only the pilot was on board.

The FAA did not disclose details of a second aircraft being involved in the accident.

Source:  http://www.wptv.com