Wednesday, November 30, 2016

Chicago O'Hare International Airport night runway plan to end on Christmas, despite pleas



City aviation officials said Wednesday that O’Hare Airport will end a six-month test of a new night runway rotation plan on Christmas morning, as originally scheduled, despite pleas by Schiller Park and Harwood Heights to extend it.

Mayors of both suburban towns east of the airport said the temporary plan to better distribute night jet noise has lessened the heavy overnight air traffic their communities shouldered after a dramatic change in O’Hare flight plans in 2013.

As a result, they said, they would like to see it continue while test results are being analyzed. The plan, launched July 6, rotates night runways every week, on a 12-week schedule, and alternates between diagonal “cross wind” runways and parallel “east-west” runways.

“Schiller Park got some relief from this and I hate to see it end,” Schiller Park Mayor Barbara Piltaver told fellow members of the Ad Hoc Fly Quiet committee of the O’Hare Noise Compatibility Commission.

The plan has reduced the night burden on Schiller Park, Harwood Heights and portions of Chicago to the east of O’Hare, as well as Bensenville and Wood Dale to the west. All are affected by O’Hare’s growing stable of east-west parallel runways. However, other suburbs, like Des Plaines, have been howling about the plan’s increased night use of diagonal runways.

Aaron Frame, of the Chicago Department of Aviation, said “chances are” running the test longer than the six months planned would trigger an environmental analysis that could last anywhere from months to a year. He cited a July 1, 2016, letter from the Federal Aviation Administration stating that “continuing the rotation plan beyond the test would be subject to future environmental review.”

FAA spokesman Tony Molinaro told the Chicago Sun-Times on Wednesday that the FAA “would consider” any city request for an extension but could not speculate on what its response would be.

Even so, Frame said the Aviation Department will end the test early Christmas morning, as planned, take the month of January to analyze the results, and then present its findings to the the Fly Quiet Committee and the Noise Commission for discussion and possible tweaking, approval or rejection.

Karen Robles of Schaumburg, a community affected by heavier night use of a diagonal runway due for demolition in 2018, favored that idea. She said there are some “tweaks many of us would like to evaluate” after the test ends and its results are thoroughly analyzed.

Mayor Craig Johnson of Elk Grove Village said later he also favors ending the plan on schedule, going back to pre-rotation night flights temporarily, and then coming up with a new six-month plan that uses the diagonal runway aimed at his village and Schaumburg less frequently.

Currently, Johnson said, Elk Grove Village carries a “disproportionate share” of night traffic and is affected in nine out of 12 weeks in the rotation.

“You shouldn’t have nine out of 12 weeks, flights going over some communities,” Johnson said.

Wednesday’s discussion indicated the Chicago area could see many changes in night flights as officials wrestle with how to proceed. But in addition, even daytime flight paths could well change again in 2019, after a diagonal runway closes; in 2020, after a new east-west parallel runway opens in the north airfield; and in 2021, when an existing parallel runway in the north airfield is due to be lengthened.

Source:   http://chicago.suntimes.com

ViaAir Now Flying Out of Shenandoah Valley Regional Airport



WEYERS CAVE, Va. (WVIR) -  The first daily regional jet service is taking off from the Shenandoah Valley Regional Airport (SHD).

Passengers waited Wednesday morning for the inaugural ViaAir flight to Charlotte, North Carolina. The plane had to divert to a different airport Tuesday night due to fog.

The 50-seat jet flew into Weyers Cave in the morning to board 21 passengers bound for Charlotte or beyond.

ViaAir is scheduled to fly out of SHD twice daily on weekdays and once a day on weekends.

“It's only about 3 miles from home and you don't have to fight the traffic and the parking and other headaches associated with going to a big airport,” said Kevin Craun, traveling to Florida.

“I like the idea of a jet. It gets to Charlotte faster and allows me to get to my final destination much faster than either going through Dulles or going to Charlottesville,” said Sue Garney.

The airport’s executive director says ticket sales have been brisk since SHD announced the new jet service late last month.

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



WEYERS CAVE — Kevin Craun and his family were among the happy passengers sitting in Shenandoah Valley Regional Airport Wednesday morning.

The Craun family of Weyers Cave was headed to Florida. The family was among the first passengers to board the airport’s initial flight on ViaAir to Charlotte-Douglas International Airport in Charlotte, North Carolina. Previously, Craun said he would have driven to Roanoke or Northern Virginia for a flight to the Sunshine State via Charlotte.

“The worst part was driving to the airport,’’ said Craun.

Now with ViaAir providing flights to both Charlotte and Orlando, Craun said he can drive three miles from his home and park for free. “Fifteen minutes after we get off the plane we’re home,” he said of the return.

Twenty one passengers boarded ViaAir Wednesday morning. Fog overnight delayed the arrival of the 50-seat jet. Airport Executive Director Greg Campbell said Tuesday night’s fog caused the plane to divert to a West Virginia location. And he said thunderstorms in West Virginia delayed the departure from 8  a.m. to  11 a.m. on Wednesday.

ViaAir will provide 12 flights weekly to and from Charlotte. And starting on Dec. 11, the airline will offer twice-weekly service to and from Orlando on Wednesdays and Sundays. SVRA announced the new agreement and service with ViaAir in October.

Airport Commission member Jeff Ward represents Waynesboro. He said offering flights to a southern hub such as Charlotte has come up often in his conversations with people.

“Everybody I’ve talked to mentioned Charlotte,’’ Ward said. “And the connections to Florida will be a big help.”

Frequent business travelers also spoke of the convenience the new flights would offer.  Sue Ganey of Harrisonburg travels by air at least once a month to Texas or Ohio.

Previously, Ganey said she would have to fly to a northeastern destination before being routed on another flight to Texas. Now, she can fly to Charlotte and head south.

“This is really nice,’’ said Ganey, who also likes the free parking at SVRA.

Source:   http://www.dailyprogress.com



It was a big day for the Shenandoah Valley Regional Airport, as the first flight from SHD to Charlotte, North Carolina took off.

A dozen people lined up to be on the first ViaAir flight to Charlotte, ND today. The flight is a quick 50 minutes, and then you are in a southeastern hub, and can go pretty much anywhere.

While this is convenient for many families, some took the flight because of the experience.

"I am very excited! I have been waiting on this day since I learned I would be going on the Inaugural flight. I have been very, very, very excited, " said Jamison McCarty.

SHD will offer flight to Orlando, Florida beginning on December 11, 2016.

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

Loss of Control on Ground: Aero Commander 690, N9175N; accident occurred November 30, 2016 at Scottsdale Airport (KSDL), Maricopa County, Arizona






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

Additional Participating Entity: 

Federal Aviation Administration / Flight Standards District Office; Scottsdale, Arizona 

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


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

http://registry.faa.gov/N9175N

Location: Scottsdale, AZ
Accident Number: WPR17LA030
Date & Time: 11/30/2016, 1730 MST
Registration: N9175N
Aircraft: AERO COMMANDER 690
Aircraft Damage: Substantial
Defining Event: Loss of control on ground
Injuries: 1 None
Flight Conducted Under: Part 91: General Aviation - Positioning 

On November 30, 2016, about 1730 mountain standard time, an Aero Commander 690, N9175N, was substantially damaged when it was involved in an accident at the Scottsdale Airport (SDL), Scottsdale, Arizona. The commercial pilot was not injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 maintenance relocation flight.

The pilot reported that after a normal landing on runway 21 he began easing the power levers into reverse and applying light braking action to slow the speed. While reaching for the condition levers to bring the propellers back to low RPM, the airplane "darted to the right." The pilot applied left braking and adjusted the engines to low RPM settings to compensate for the veer. Despite his actions, the airplane continued to veer towards the right side of the runway and was approaching the A11 exit sign. The pilot reported that he could have either gotten more aggressive with the corrective actions, and hope to avoid striking the sign, or allow the airplane to exit the runway on what he thought was a hard smooth surface. The pilot chose to exit the runway surface which was the runway safety area (RSA). Once the airplane entered the RSA, the landing gear sunk deep into the rocks which quickly slowed the airplane to a stop.

Security cameras captured the airplane during landing. The airplane touched down near the 1,000 ft runway distance markers and about 1,300 ft further, exited near taxiway A11. The airplane traveled about 50 ft into the RSA, creating deep troughs through the rock layer, and came to a stop about 2,500 ft from the approach end of runway 1.

A postaccident examination of the airplane revealed impact damage to the left side of the fuselage. The impact damage consisted of multiple holes and dents in the fuselage cabin passenger area and window areas. A rock about 2 inches in length was found imbedded in the fuselage and could not be removed during the examination. Several rocks penetrated the passenger area, one impacting the right side window from the inside. The propeller blades had gouging on the leading edges from the midsections to the tips. The right landing gear brake rotor showed light gouging on the braking surface.

The flight control system was examined, and all flight controls moved freely with unobstructed movement. The steering system was operated with the activation of the hydraulic system and the nose landing gear tire was positioned over a grease plate. Actuation of the brakes produced normal steering operation. No evidence of any mechanical malfunctions or failures were revealed that would have precluded normal operation.

The RSA rock layer consisted of about 3-inch sized smoothed river rock. The depth of the rock layer varied from 4-inches to 12-inches deep through the area of the accident site.
Accident Site and Runway Tire Marks

According to the FAA, RSAs are not designed with a particular aircraft in mind. RSA's are designed to provide all aircraft types with the space and time needed to safely come to a stop while avoiding fixed obstacles on the airport that may damage the aircraft and potentially injure or kill the occupants. RSAs are designed to support the aircraft without sinking into the soil and causing an abrupt halt. RSAs can be made of many materials, including rocks. These rocks should be no larger than four inches in size. RSAs, like any other landing/runway ground surface, are not designed for contact by any part of the aircraft other than the landing gear. The design of an RSA does not take into consideration contact by propellers, engines, wings, etc. RSAs around the country have proven to be effective at mitigating damage, injury, and death when runway excursions and overruns occur.

According to the Department of Transportation Advisory Circular (AC 150/5300-13A)- An RSA is defined as a surface surrounding the runway prepared or suitable for reducing the risk of damage to aircraft in the event of an undershoot, overshoot, or excursion from the runway. Also, FAA Order 5200.8, defines that RSA is intended to provide a measure of safety in the event of an aircraft's excursion from the runway by significantly reducing the extent of personal injury and aircraft damage during overruns, undershoots and veer-offs. SDL RSA design and specification drawings show a crushed aggregate depth of 4 inches. 

Pilot Information

Certificate: Commercial
Age: 63, Male
Airplane Rating(s): Multi-engine Land; Single-engine Land
Seat Occupied: Left
Other Aircraft Rating(s): None
Restraint Used:
Instrument Rating(s): Airplane
Second Pilot Present: No
Instructor Rating(s): None
Toxicology Performed: No
Medical Certification: Class 2 Without Waivers/Limitations
Last FAA Medical Exam: 02/11/2016
Occupational Pilot: Yes
Last Flight Review or Equivalent:
Flight Time:  4654 hours (Total, all aircraft), 322 hours (Total, this make and model), 4654 hours (Pilot In Command, all aircraft), 21 hours (Last 90 days, all aircraft)

Aircraft and Owner/Operator Information

Aircraft Make: AERO COMMANDER
Registration: N9175N
Model/Series: 690 UNDESIGNATED
Aircraft Category: Airplane
Year of Manufacture: 1973
Amateur Built: No
Airworthiness Certificate: Normal
Serial Number: 11071
Landing Gear Type: Retractable - Tricycle
Seats: 7
Date/Type of Last Inspection:  AAIP
Certified Max Gross Wt.:10251 lbs 
Time Since Last Inspection:
Engines: 2 Turbo Prop
Airframe Total Time:
Engine Manufacturer: Honeywell
ELT: Installed, not activated
Engine Model/Series: TPE 331-5
Registered Owner: AIR WEST INC
Rated Power: 715 hp
Operator: AIR WEST INC
Operating Certificate(s) Held:  On-demand Air Taxi (135)

Meteorological Information and Flight Plan

Conditions at Accident Site: Visual Conditions
Condition of Light: Dusk
Observation Facility, Elevation: KSDL, 1473 ft msl
Distance from Accident Site: 1 Nautical Miles
Observation Time: 2353 UTC
Direction from Accident Site: 43°
Lowest Cloud Condition: Clear
Visibility:  10 Miles
Lowest Ceiling: None
Visibility (RVR):
Wind Speed/Gusts: Calm /
Turbulence Type Forecast/Actual:
Wind Direction:
Turbulence Severity Forecast/Actual:
Altimeter Setting: 29.99 inches Hg
Temperature/Dew Point: 16°C / -8°C
Precipitation and Obscuration: No Obscuration; No Precipitation
Departure Point: SAFFORD, AZ (SAD)
Type of Flight Plan Filed: Company VFR
Destination: SCOTTSDALE, AZ (SDL)
Type of Clearance: VFR; VFR Flight Following
Departure Time: 1700 MST
Type of Airspace: Class D

Airport Information

Airport: SCOTTSDALE (SDL)
Runway Surface Type: Asphalt
Airport Elevation: 1510 ft
Runway Surface Condition: Dry
Runway Used: 21
IFR Approach: None
Runway Length/Width: 8249 ft / 100 ft
VFR Approach/Landing: Full Stop; Traffic Pattern

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: 33.613611, -111.921389 (est)

NTSB Identification: WPR17LA030
14 CFR Part 91: General Aviation
Accident occurred Wednesday, November 30, 2016 in Scottsdale, AZ
Aircraft: AERO COMMANDER 690, registration: N9175N
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 November 30, 2016, about 1730 mountain standard time, an Aero Commander 690, N9175N, was substantially damaged during a runway excursion after landing at the Scottsdale Airport (SDL), Scottsdale, Arizona. The airplane was registered to and operated by Air West Inc., and was on a maintenance relocation flight conducted under the provisions of 14 Code of Federal Regulations Part 91. The airline transport pilot was the sole occupant, and was not injured. Visual meteorological conditions prevailed, and no flight plan was filed for the flight. The flight originated from Safford Regional Airport, Safford, Arizona, about 1700.

According to the pilot, the landing on runway 21 was normal and he intended to exit to a taxiway left of the runway; however, shortly after applying reverse thrust, the airplane veered to the right. The pilot applied corrective actions (rudder and brake) to compensate for the veer, but subsequently made a decision to enter the runway safety area (RSA) near taxiway A11, to avoid hitting a runway sign. He also stated that as the airplane entered the RSA, the landing gear sunk deep into the sand and rock. As the airplane came to a stop, about 30 feet into RSA, both propeller blades contacted sand and rocks. The left propeller blades impacted fist sized river rocks sending shards into the left side of the fuselage. The RSA material in this area consisted of about 6 inches of sand and rock covering a layer of fist sized river rock.

The airplane was removed from the RSA, and towed to a non-movement area on the airport.

According to a Federal Aviation Administration inspector, the left side of the fuselage had impact damage. Several rocks had entered the fuselage through the skin and side windows from the pilot seat rearward to below the wing. Several structural members were compromised from the damage.




SCOTTSDALE, AZ - Scottsdale Airport is currently closed after a twin-engine plane veered off the runway Wednesday evening.

Sarah Ferrara, spokesperson for the airport, said the plane left the runway and went about 30 feet into some rocks.

One person was aboard the plane and "appears to be fine," she said in an email to ABC15. The airport's runway was not damaged, she said.

Crews were working to remove the aircraft so the airport could reopen.

Air15 video showed the plane just off the runway with emergency crews nearby.

The airport is located near Scottsdale Road and Frank Lloyd Wright Blvd.

National Oceanic and Aeronautic Administration Hurricane Hunters moving staff, fleet of planes to Lakeland Linder Regional Airport



LAKELAND — Scientific sorties into tropical cyclones will launch from Lakeland Linder Regional Airport starting next year.

The National Oceanic and Aeronautic Administration Hurricane Hunters weather squadron will be moving its staff of about 100 and fleet of nine aircraft — including its modified P-3 Orions "Kermit" and "Miss Piggy" — to Lakeland Linder after May 1, the city announced Wednesday.

For NOAA, the deal supplies a nearby base of operations after the Air Force chose not to continue its current arrangement at MacDill Air Force Base after next year.

In exchange, Lakeland Linder gains a high-profile tenant — and a major boost to its annual revenues that will help it fund and market its bid to become a major center for high-skill and high-wage jobs in the county.

"This is probably one of our most significant wins over the last ten to twenty years," Airport Manager Gene Conrad said. St. Pete-Clearwater International Airport also bid for the contract.

NOAA will pay Lakeland Linder about $6.8 million to lease the Airside Center at 3450 Flightline Drive — roughly 105,000 square feet of space — for five years. The contract includes an optional extension that would yield $5.8 million through the second five-year term.

This is roughly three times what the airport was earning per square foot from the previous lease, which ended when the company was evicted for not paying rent. It's also about a 15 percent jump for the airport's total annual revenues. The airport sustains itself from its own business revenues, not taxes.

"This type of lease opportunity is rare and the long term significance of being awarded the contract is far greater than just the rental revenue that LLRA will receive," the city's staff wrote to commissioners in a memo, encouraging them to accept the deal.

City Manager Tony Delgado, who started his career in the live entertainment business, said landing the NOAA Hurricane Hunters is the equivalent of a "prestige account," the kind of act with a reputation that will draw more interest to the facility.

The Air Force declining to keep NOAA on its base created the opportunity, but Lakeland Linder was prepared when it arose, Conrad said.

"A lot had to occur to make this happen."

Without Lakeland Linder's long runway, a new air traffic control tower and an aircraft rescue and firefighting facility on its edge, "NOAA wouldn't be here," he said.

Grants from state and federal transportation authorities — and a willingness by the City Commission to support ambitious projects — have enabled about $100 million in improvements at the airport since 2010.

"We've finally turned the corner in people's minds," Delgado said, and they are now seeing Lakeland Linder as an "economic driver."

About 1,000 are employed in high-skill, high-wage jobs in businesses on the airport property, Conrad said. Roughly half of those work in the aviation sector. The NOAA contract will add another 100 aviation-sector jobs, plus the city expects contractors and suppliers that work with the squadron may eventually look to relocate as well.

And outside that supply chain, "growth will always attract growth," said John Von Preysing, the airport's business manager.

The aviation education pipeline on the south side of the airport, with Polk State College and the Central Florida Aerospace Academy, also makes a strong argument for aviation companies to move to Lakeland, Von Preysing added.

Pursuing the NOAA contract was somewhat of a gamble for the airport.

When NOAA announced its need for a new airbase, the city took funds it had appropriated for the MRO facility and poured them into its Airside Center in the hopes of landing the federal contract.

"By investing in an existing facility, it allowed us to accelerate growth," Von Preysing said.

"It was just one of those risks you had to take," Delgado added.

With the contract secured, Lakeland Linder will use the profits to continue developing a new, large maintenance facility on the north side of the airport. The planned "MRO facility," for maintenance, repair and overhaul, will accommodate mainline commercial passenger jets.

If built out as initially planned, the MRO facility could add another 300 to 400 technical jobs to the airport. Conrad and airport executives have been actively courting suitable businesses, but have remained quiet about the details of those conversations.

Story and photo gallery:   http://www.theledger.com

Close Calls on United States Airport Runways Rise Sharply: Hazardous incidents substantially surpassed federal safety standards in five months of latest year



The Wall Street Journal
By ANDY PASZTOR
Nov. 30, 2016 2:23 p.m. ET


Hazardous runway incidents at U.S. airports in fiscal 2016 increased for the third year in a row, significantly exceeding federal safety targets in five of those months and climbing 25% overall from a year earlier.

Both the raw numbers and frequency of the most dangerous types of close calls on the ground rose significantly in the federal fiscal year ended Sept. 30, according to preliminary government data that hasn’t yet been widely distributed. The jump came despite stepped-up federal and industry efforts to reverse the trend.

Federal Aviation Administration officials said in total, there were more than 1,560 instances nationwide when planes came closer than permitted to each other, or to vehicles, on the tarmac. That’s up from about 1,450 in fiscal 2015 and roughly 1,250 in 2013 and 2014.

For the latest year as a whole, the rate of the highest-risk incidents, adjusted for monthly fluctuations in air traffic, barely met the agency’s internal, long-established limit of about four such “runway incursions” per 10 million flights; they substantially exceeded the limit in five of the 12 months. The FAA’s strategic plan calls for compliance with that cap through at least September 2017.

The comparable rate for fiscal 2015 came in at roughly three serious events per 10 million flights, and hovered well below the rate stretching back to 2013.

Despite years of initiatives to combat such threats—including a high-profile campaign rolled out earlier this year—the most dangerous categories of runway incursions continued to increase in fiscal 2016. According to the FAA, there were 19 close calls resulting in significant chances of accidents or collisions that were narrowly avoided, versus 15 the year before.

The statistics cover airliners, business jets and private aircraft at airports with towers across the country. With some 700 million passengers getting on U.S. carriers every year and roughly 30,000 commercial flights in the air each day, runway errors amount to a tiny sliver of that total.

The FAA recorded nearly 50 million flights of all aircraft nationwide in fiscal 2016, while there hasn’t been a major runway collision of big planes on a U.S. strip in recent memory.

Still, annual runway incursion statistics are considered an important benchmark of aviation safety. They are closely watched by experts inside and outside the FAA as harbingers of hazardous trends and impending threats.

That’s partly because commercial aviation has become so safe there hasn’t been a single passenger fatality from the crash of a scheduled U.S. airliner in seven years. Statistically, experts say the most dangerous portion of any airliner flight is the time spent taxiing on the ground.

Runway safety is equally daunting in Europe. In the past decade, nearly one out of five fatal accidents involved runway incursions, according to the European Aviation Safety Agency’s 2016 statistical review.

Runway incidents depend on a host of factors, from the level of traffic to airport layouts to lighting and signs on the tarmac. Variations among local controller procedures also have an impact. In fiscal 2016, pilot mistakes were roughly three times more likely to cause incursions than air-traffic controller errors, based on FAA numbers.

Federal officials and industry safety experts have had a roller-coaster history combating close calls between planes on the ground. In fiscal 2008, with the number of runway incursions climbing to a five-year high, FAA leaders invoked a nationwide “call to action” to deal with the problem. Rates for the most serious incidents dropped sharply in the next two years, spiked in 2012 and then went down again.

Earlier this year however, both the FAA and the National Transportation Safety Board, which investigates aviation accidents and incidents, became concerned again about the stubborn upward trend. Renewing focus on the hazards, the FAA boosted efforts to analyze incident patterns, enhance pilot education and help airport operators mitigate specific risks.

Across the U.S., busy airports already have installed special lights designed to alert crews before planes mistakenly taxi onto an active runway. Similarly, plane manufacturers and cockpit-equipment suppliers have devised various systems intended to warn pilots if they line up to land or take off on an incorrect strip.

Nonetheless, the latest numbers highlight the challenges of reducing the most pressing runway risks, even if the total number of incursions starts to go down. During several months of 2016 when overall incursion numbers stayed basically flat, the rate for the highest-risk incidents nevertheless exceeded maximum FAA targets by double-digit margins.

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

Cessna 560, N22AF: Incident occurred November 28, 2016 at Salinas Municipal Airport (KSNS), Monterey County, California

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

Additional Participating Entity: 

Federal Aviation Administration / Flight Standards District Office; San Jose, California

Registered to Bill Massa Company Incorporated


http://registry.faa.gov/N22AF

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

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

Location: Salinas, CA
Incident Number: GAA17IA083
Date & Time: 11/28/2016, 2030 PST
Registration: N22AF
Aircraft: CESSNA 560
Aircraft Damage: Minor
Defining Event: Abrupt maneuver
Injuries: 1 None
Flight Conducted Under:  Part 91: General Aviation - Personal 

On November 28, 2016, at 2030 Pacific standard time, after landing and after transitioning from taxiway Foxtrot to a taxilane, a Cessna 560 airplane, N22AF, struck a helicopter, N530PJ, that was parked in a non-movement area at Salinas Municipal Airport, Salinas, California. The airplane sustained minor damage to the right-wing tip and the pilot was not injured, but the helicopter required major repair. The airplane was registered to Bill Massa Company Incorporated, Salinas, California, and operated under 14 Code of Federal Regulations Part 91, as a night, visual flight rules flight. The flight originated from Salinas, California and had returned to Salinas.

According to the pilot, he landed the airplane and taxied to his hangar. The pilot reported that he utilized taxiway Foxtrot and had made a right turn into the transient parking area heading southeast, via the taxilane. He recalled that he was concerned with remaining a safe distance from an airplane that was parked on the left side of the taxilane, and turned the airplane to the right, away from the taxilane centerline, and the airplane's right wing struck a helicopter that was parked on the right side of the taxilane.

Federal Aviation Administration, Advisory Circular 150/5300A, Airport Design, page 124, Table 4-1 Design standards based on Airplane Design Group (ADG), denotes that Salinas Municipal Airport is a Category B-II airport. B-II design standards denote a 57-foot, 5 inch Taxilane Object Free Area (TOFA), on either side of the taxilane centerline.

The airplane that the pilot attempted to avoid was parked on the left side of the taxilane centerline within the limits of the TOFA. The airport manager had authorized aircraft parking within the area of the TOFA. 

Pilot Information

Certificate: Airline Transport; Commercial
Age: 74, Male
Airplane Rating(s): Multi-engine Land; Single-engine Land
Seat Occupied:
Other Aircraft Rating(s): None
Restraint Used:
Instrument Rating(s): Airplane
Second Pilot Present: No
Instructor Rating(s): Airplane Single-engine
Toxicology Performed: No
Medical Certification: Class 2 With Waivers/Limitations
Last FAA Medical Exam: 01/16/2017
Occupational Pilot: Yes
Last Flight Review or Equivalent:
Flight Time:   0 hours (Total, all aircraft), 0 hours (Total, this make and model) 

Aircraft and Owner/Operator Information

Aircraft Manufacturer: CESSNA
Registration: N22AF
Model/Series: 560 CITATION
Aircraft Category: Airplane
Year of Manufacture: 1991
Amateur Built: No
Airworthiness Certificate: Normal
Serial Number: 560-0129
Landing Gear Type: Tricycle
Seats: 9
Date/Type of Last Inspection:
Certified Max Gross Wt.:  16300 lbs
Time Since Last Inspection:
Engines: 2 Turbo Fan
Airframe Total Time:
Engine Manufacturer:  P&W CANADA
ELT:
Engine Model/Series: JT15D-5
Registered Owner: BILL MASSA CO INC
Rated Power: 374 lbs
Operator: BILL MASSA CO INC
Operating Certificate(s) Held: None 

Meteorological Information and Flight Plan

Conditions at Accident Site: Visual Conditions
Condition of Light: Night
Observation Facility, Elevation: KSNS, 77 ft msl
Observation Time: 0453 UTC
Distance from Accident Site: 0 Nautical Miles
Direction from Accident Site: 313°
Lowest Cloud Condition: Clear
Temperature/Dew Point: 10°C / 6°C
Lowest Ceiling: None
Visibility:  10 Miles
Wind Speed/Gusts, Direction: 5 knots, 250°
Visibility (RVR):
Altimeter Setting: 30.03 inches Hg
Visibility (RVV):
Precipitation and Obscuration: No Obscuration; No Precipitation
Departure Point:  Salinas, CA (SNS)
Type of Flight Plan Filed: None
Destination: Salinas, CA (SNS)
Type of Clearance: None
Departure Time:  PST
Type of Airspace: Class D 

Airport Information

Airport:  SALINAS MUNI (SNS)
Runway Surface Type: N/A
Airport Elevation: 84 ft
Runway Surface Condition: Dry
Runway Used: N/A
IFR Approach: None
Runway Length/Width:
VFR Approach/Landing: None

Wreckage and Impact Information

Crew Injuries: 1 None
Aircraft Damage: Minor
Passenger Injuries: N/A
Aircraft Fire: None
Ground Injuries: N/A
Aircraft Explosion: None
Total Injuries: 1 None

Latitude, Longitude:  36.662778, -121.606389 (est)

NTSB Identification: GAA17IA083 
14 CFR Part 91: General Aviation
Incident occurred Monday, November 28, 2016 in Salinas, CA
Aircraft: CESSNA 560, registration: N22AF
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 used data provided by various sources and may not have traveled in support of this investigation to prepare this aircraft incident report.

On November 28, 2016, at 2030 Pacific standard time, a Cessna 560 airplane, N22AF, struck a helicopter that was parked in designated transient parking area at Salinas Municipal Airport, Salinas, California. The airplane sustained minor damage to the right wing and the pilot was not injured, but the helicopter required major repair. The airplane was registered to Bill Massa Company Incorporated, Salinas, and operated under 14 Code of Federal Regulations Part 91, as a visual flight rules flight. Visual meteorological conditions prevailed for the flight. The flight originated from Salinas, California and had returned to Salinas, California.

During the incident investigation the pilot reported that he turned to the right to avoid an airplane that was too close to the taxi lane centerline. There is a specific distance from the taxi lane centerline that obstacles must remain clear of. The area is defined as the Taxiway/Taxi lane Object Free Area (TOFA). The airplane that the pilot attempted to avoid and the helicopter that was struck, occupied the TOFA. The dimensions of the TOFA do not appear to meet Federal Aviation Administration Airport Design standards, specifically Airport Certification requirements specified per Title 14, Code of Federal Regulations, Part 139. 

The investigation is continuing.

Vans RV-8, EXA LLC, N880KM: Accident occurred November 22, 2016 in Roopville, Carroll County, Georgia

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 

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

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

EXA LLC:  http://registry.faa.gov/N880KM

FAA Flight Standards District Office: FAA Atlanta FSDO-11

NTSB Identification: GAA17CA085
14 CFR Part 91: General Aviation
Accident occurred Tuesday, November 22, 2016 in Roopville, GA
Probable Cause Approval Date: 02/06/2017
Aircraft: HUNDLEY MICHAEL J VANS RV8, registration: N880KM
Injuries: 2 Uninjured.

NTSB investigators used data provided by various entities, including, but not limited to, the Federal Aviation Administration and/or the operator and did not travel in support of this investigation to prepare this aircraft accident report.

The pilot of the tailwheel equipped airplane reported that during the 3-point landing, the airplane drifted to the left and he applied right correction. He further reported that he “obviously over corrected” because the airplane went to the right and he was unable to correct with left rudder and brake. The airplane exited the runway and impacted trees. 

The airplane sustained substantial damage to both wings and the fuselage.
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 conducted a wheel landing to provide more directional control during the landing roll.

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

The pilot’s overcorrection with the right rudder during the landing roll, which resulted in a loss of directional control and a runway excursion.

For Some, Property Assessment Reductions Do Little To Ease Tax Concerns: Des Plaines Alderman Wants More Information On Chicago O'Hare International Airport Noise Study

Even with an Equalized Assessed Value (EAV) reduction from Cook County, most Des Plaines residents plagued with loud overnight airport noise saw an increase in their overall property taxes this year.

According to Ald. Malcolm Chester (6th), the Cook County Assessor’s Office has been conducting a study for two years to lower the EAV of homes in portions of the county that experience heavy air traffic. EAV is a value placed on property for tax purposes, determined by an equalization factor that allows all properties in the region to be uniformly assessed, according to the Illinois Department of Revenue.

This year, Chester’s home in the city’s south side 6th ward received a 7% decrease in EAV as a result of its location under an O’Hare Airport noise path. However, this decrease was surpassed by the overall 9% increase in EAV for the property since its last assessment, so Chester actually saw his EAV rise approximately 2%.

“This is Cook County’s version of tax relief,” said Chester in a newsletter to his constituents.

“Market values went down with the recession,” he said of the EAV increase on Wednesday, Nov. 16, “and of course, now they are going back up.”

Others in the ward have come to Chester with similar complaints of rising EAV, despite the decrease for noise from Cook County. Additionally, the rate of decrease for airplane noise was not consistent in the area. While Chester received a 7% decrease, some of his neighbors received 4% and others received none.

“We’ve asked to see the study and asked to have it explained to us,” Chester said. He added that O’Hare Noise Compatibility Commission (ONCC) Chair and Mount Prospect Mayor Arlene Juracek has requested details of the study from Cook County.

“The assessor has not yet told any of us on the commission what the criteria are for granting this reduction in assessed value,” said Chester in his newsletter.

Another issue for Des Plaines residents who live under the hull of O’Hare flights is the proposed “Fly Quiet Rotation,” which is currently being tested. The final round of the six-month testing cycle is scheduled to end on Christmas. During this 12-week cycle, jets will fly over Des Plaines’ 6th, 2nd and 1st ward homes at night to land at Runway 22-R for three weeks.

Although Des Plaines residents have adapted to flights landing and taking off from Runway 22-R for years, Chester said that night noise is “a whole different ball game.”

After data from the rotation test has been collected by the Federal Aviation Administration (FAA) a decision will be made, most likely by the end of the year, on making the Fly Quiet rotation permanent. Although Chester intends to fight for a return to the old flight schedule, he admits that there are a variety of factors working against Des Plaines.

“We don’t really have a lot of allies,” he said. According to Chester, other areas affected by the Fly Quiet Rotation, such as Park Ridge and Glenview, will most likely benefit from the change. “It’s an isolating position to be in.”

At this point, one of the only things that could protect the former rotation schedule would be safety issues regarding Runway 22-R. As one of the airport’s oldest runways, 22-R is relatively short at 7,500 ft., which makes landing planes on the strip at night, or during winter weather conditions, a dangerous prospect. Chester noted that the recent incident where an American Airlines flight caught fire may have faced dire consequences on a short runway.

If the Fly Quiet Rotation is eventually approved by the FAA, Chester hopes that residents will have access to federal funding for noise insulation measures.

“We’ll have to wait it out and watch it carefully,” Chester said.

Source:  http://www.journal-topics.com

Evolution Revo, Sport Aviation Center LLC, N31PH: Accident occurred October 20, 2016 in Carson City, Nevada

Location: Carson City, NV 
Accident Number: GAA17CA039
Date & Time: 10/20/2016, 0815 PDT
Registration: N31PH
Aircraft: EVOLUTION AIRCRAFT INC REVO
Aircraft Damage: Substantial
Defining Event: Loss of control on ground
Injuries: 2 None
Flight Conducted Under: Part 91: General Aviation - Instructional

Analysis 

The flight instructor in the weight shift aircraft, which was equipped with a floor mounted, foot operated throttle, reported that upon startup, the pilot receiving instruction inadvertently applied full throttle while putting his right foot on the pedal power control unit. Subsequently, the weight shift aircraft started to move towards a parked jet, so the flight instructor turned the aircraft sharply and the aircraft tipped onto its side.

The weight shift aircraft sustained substantial damage to both wings.

The flight instructor reported that there were no pre impact mechanical failures or malfunctions with the airframe or engine that would have precluded normal operation. 

Probable Cause and Findings

The National Transportation Safety Board determines the probable cause(s) of this accident to be:
The pilot receiving instruction's inadvertent application of throttle during the engine start, which led to an inadvertent acceleration and a roll-over. 

Findings

Aircraft
Aircraft power plant - Unintentional use/operation (Cause)

Personnel issues
Aircraft control - Student pilot (Cause)

Factual Information

History of Flight

Standing-engine(s) start-up
Loss of control on ground (Defining event)
Attempted remediation/recovery 

Flight Instructor Information

Certificate: Flight Instructor; Private; Sport Pilot
Age: 60, Male
Airplane Rating(s): Single-engine Land
Seat Occupied: Rear
Other Aircraft Rating(s): None
Restraint Used: Lap Only
Instrument Rating(s): None
Second Pilot Present: Yes
Instructor Rating(s): Airplane Single-engine
Toxicology Performed: No
Medical Certification: Sport Pilot Without Waivers/Limitations
Last FAA Medical Exam:
Occupational Pilot: Yes
Last Flight Review or Equivalent: 06/05/2015
Flight Time: (Estimated) 4960 hours (Total, all aircraft), 470 hours (Total, this make and model), 4900 hours (Pilot In Command, all aircraft), 160 hours (Last 90 days, all aircraft), 40 hours (Last 30 days, all aircraft), 2 hours (Last 24 hours, all aircraft) 

Pilot Information

Certificate: Sport Pilot
Age: 75, Male
Airplane Rating(s): Single-engine Land
Seat Occupied: Front
Other Aircraft Rating(s): None
Restraint Used: 3-point
Instrument Rating(s): None
Second Pilot Present: Yes
Instructor Rating(s): None
Toxicology Performed: No
Medical Certification: Sport Pilot Unknown
Last FAA Medical Exam:
Occupational Pilot: No
Last Flight Review or Equivalent: 10/29/2014
Flight Time: (Estimated) 175 hours (Total, all aircraft), 1 hours (Total, this make and model), 150 hours (Pilot In Command, all aircraft), 10 hours (Last 90 days, all aircraft), 5 hours (Last 30 days, all aircraft), 1 hours (Last 24 hours, all aircraft) 

Aircraft and Owner/Operator Information

Aircraft Manufacturer: EVOLUTION AIRCRAFT INC
Registration: N31PH
Model/Series: REVO
Aircraft Category: Weight-Shift
Year of Manufacture: 2015
Amateur Built: No
Airworthiness Certificate: Special Light-Sport
Serial Number: 000611
Landing Gear Type: Tricycle
Seats: 2
Date/Type of Last Inspection: 07/20/2016, Annual
Certified Max Gross Wt.: 1160 lbs
Time Since Last Inspection:
Engines: 1 Reciprocating
Airframe Total Time: 72 Hours at time of accident
Engine Manufacturer: Rotax
ELT: Not installed
Engine Model/Series: 912iS
Registered Owner: On file
Rated Power: 100 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: KCXP, 4699 ft msl
Observation Time: 1515 UTC
Distance from Accident Site: 1 Nautical Miles
Direction from Accident Site: 173°
Lowest Cloud Condition: Clear
Temperature/Dew Point: 2°C / 0°C
Lowest Ceiling: None
Visibility:  10 Miles
Wind Speed/Gusts, Direction: Calm
Visibility (RVR): 
Altimeter Setting: 30.38 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: 0815 PDT
Type of Airspace: Class G 

Airport Information

Airport: CARSON (CXP)
Runway Surface Type: Asphalt
Airport Elevation: 4704 ft
Runway Surface Condition: Dry
Runway Used: N/A
IFR Approach: None
Runway Length/Width:
VFR Approach/Landing: None 

Wreckage and Impact Information

Crew Injuries: 2 None
Aircraft Damage: Substantial
Passenger Injuries: N/A
Aircraft Fire: None
Ground Injuries: N/A
Aircraft Explosion: None
Total Injuries: 2 None
Latitude, Longitude: 39.195556, -119.735000 (est)

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

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

SPORT AVIATION CENTER LLC: http://registry.faa.gov/N31PH

NTSB Identification: GAA17CA039
14 CFR Part 91: General Aviation
Accident occurred Thursday, October 20, 2016 in Carson City, NV
Aircraft: EVOLUTION AIRCRAFT INC REVO, registration: N31PH
Injuries: 2 Uninjured.

NTSB investigators used data provided by various entities, including, but not limited to, the Federal Aviation Administration and/or the operator and did not travel in support of this investigation to prepare this aircraft accident report.

The flight instructor in the weight shift aircraft, which was equipped with a floor mounted, foot operated throttle, reported that upon startup, the pilot receiving instruction inadvertently applied full throttle while putting his right foot on the pedal power control unit. Subsequently, the weight shift aircraft started to move towards a parked jet, so the flight instructor turned the aircraft sharply and the aircraft tipped onto its side.

The weight shift aircraft sustained substantial damage to both wings.

The flight instructor reported that there were no pre impact mechanical failures or malfunctions with the airframe or engine that would have precluded normal operation.