Friday, November 28, 2014

The lure of tax breaks: Colorado Springs Airport (with video)

Anyone who questions the wisdom of tax breaks to encourage business development might want to chat with Jeff Perkins and Britt Ham.

Perkins works with a company that relocated from North Carolina to an area near the Colorado Springs Airport, in part because of tax breaks approved by city, county and state officials to encourage economic development at or near the airport.

Ham is president and CEO of a company near the airport that is expanding, thanks to the tax breaks.

Together, the companies employ more than 40 people, and they're planning to add another 75 employees - the bottom-line goal of the tax breaks.

The tax breaks are a "huge incentive" for Trine Aerospace LLC to expand in the Springs, Ham said. Trine, which moved to Colorado Springs from Chatsworth, Calif., last year, has grown from about a dozen employees to 20 and has up to eight contract workers.

"It gives us an advantage over other companies," Ham said of the incentives. "The benefit is to lower our cost and allow us to bring business to Colorado Springs. We have to compete for business and, as a new business, that competition is often based on price. We are a quality vendor at a significantly lower price."

Trine plans to expand to 50 employees by the end of 2016, and company officials are studying whether to consolidate space in five hangars at the airport into a single 60,000-square-foot hangar they would build nearby, Ham said.

Perkins, vice president of business management for Rampart Aviation LLC, said the tax breaks were one of several factors that prompted owner Tony Porterfield to move the company from the Raleigh, N.C., area to the Springs. The company specializes in providing flight services, aircraft maintenance and aviation training support mostly for military units for parachute drops. It has 20 local employees and plans to add another 25 in the next year, Perkins said.

Deals hinged on tax breaks

Both companies came to the Springs as Mayor Steve Bach and airport officials were developing a series of tax breaks to lure aviation and aerospace companies to the airport to provide jobs for local residents and generate income for the facility. Any income the airport generates from leasing existing hangars or from land for new hangars helps pay its operating expenses and cuts the amount that airlines pay in landing fees - a potential way to lure more flights to a facility that has seen traffic drop dramatically.

Besides the expansions by Rampart and Trine, the airport also has leased two long-vacant facilities - one that will house a vintage aircraft collection and the other that will be used by a company that plans to convert aircraft once used by airlines for military use, bringing at least 20 more jobs to the airport.

Dan Gallagher, the airport's director, said all four deals depended on the tax breaks, which include city and county exemptions or credits for sales and use taxes paid by businesses that lease, sell, repair or maintain aircraft.

Gallagher said at least two other companies are showing interest, as a result of the tax breaks, in 200 acres on the airport's west side for potential sites of hangars they would build for aircraft modification and conversion that could eventually employ thousands of workers.

"Our future appears to be aircraft integration, or bringing older planes to today's navigational and technical standards, including engine modifications and winglets to make the aircraft more fuel efficient," Gallagher said. "We have a great opportunity to take advantage of this developing industry and we have enough land available to create thousands of additional jobs" in that industry.

Aviation and aerospace manufacturers also have shown increased interest because of the tax breaks in building plants or other facilities in the airport's 900-acre Cresterra business park that has long been envisioned by local officials as an economic hub for the region.

The tax breaks aren't the airport's only recruiting tool. Parts of both the business park and the west side of the airport, which is home to a series of hangars for private and corporate aircraft, are designated as a foreign trade zone. Such zones allow businesses to delay, reduce or even avoid U.S. Customs duties, which are imposed on imported raw materials, parts and equipment brought into the zone, lowering operating costs for any businesses located in a zone.

But the tax breaks are considered a bigger draw.

Bach began pushing for tax breaks at the airport shortly after Gallagher was named interim airport director early last year as a way to help turn around declining airline service by finding other revenue sources that would lower costs for carriers at the airport. He said attracting businesses and jobs to the airport could help jump-start economic development in all of southeast Colorado Springs, the city's most economically struggling area.

"Companies in aviation and aerospace-related industries won't come to our airport unless we can give them some kind of targeted incentive to help them get started here," Bach said.

"We are using performance-based incentives to attract and retain employers at this airport."

Aircraft owners fled airport


Plans for the tax breaks grew out of an exodus of aircraft from the Springs airport that began when the city started charging sales and use tax on aircraft, parts and related equipment.

Owners moved more than 60 aircraft to Meadow Lake Airport near Falcon, Centennial Airport in Englewood and others along the Front Range. Most other cities with airports specializing in private and corporate aviation had waived or rebated such taxes, putting the Springs airport at a disadvantage.

The Colorado Springs City Council voted 7-2 in April to create a commercial aeronautical zone that allows businesses in and around the airport that lease, sell, repair or maintain aircraft to be exempt from most city sales and use taxes.

El Paso County commissioners in August unanimously approved the zone in the same areas to give credits for sales tax paid by businesses on equipment and supplies used in maintaining, retrofitting and upgrading aircraft.

The Colorado Office of Economic Development & International Trade in September designated the airport as a aviation development zone, which makes aviation and aerospace businesses at the airport eligible for a state income tax credit of $1,200 for each newly hired employee.

Airport officials also have asked the Pikes Peak Rural Transportation Authority to exclude 1,023.6 acres on the airport's west side and in the business park from its borders so airport businesses won't have to pay the authority's 1 percent sales tax.

The authority has scheduled a public hearing Dec. 10 on the request.

COMMERCIAL AERONAUTICAL ZONE TIMELINE


2007: City of Colorado Springs begins charging aircraft owners a 2.5 percent sales tax on the value of aircraft based at the Colorado Springs Airport.

2008-13: Owners of 62 aircraft, about 20 percent of the 292 aircraft based at the airport, move them to Meadow Lake Airport near Falcon, Centennial Airport in Englewood and other airports along the Front Range.

March 2013: Mayor Steve Bach appoints Dan Gallagher as interim director of the Colorado Springs Airport following the resignation of Mark Earle and begins discussions about offering tax breaks to lure aircraft owners and aviation-
related businesses back to the airport.

April: Colorado Springs City Council votes 7-2 to create a commercial aeronautical zone in and around the airport that allows businesses selling, repairing or maintaining aircraft to be exempt from most city sales and use taxes.

August: El Paso County commissioners unanimously approve a similar zone offering sales tax credits for equipment and supplies used in maintaining, retrofitting and upgrading aircraft.

September: Colorado Office of Economic Development & International Trade approves Colorado Springs Airport as an aviation development zone where aviation and aerospace businesses can get a $1,200 state income tax credit for each new employee.

Dec. 10: Pikes Peak Rural Transportation Authority will hold a public hearing and vote whether to exclude 1,023.6 acres on the airport's west side and in its business park from its borders so businesses in those areas won't have to pay its 1 percent sales tax.

Story, Photos and Video:  http://gazette.com

Colorado Springs Airport amnesty boxes get their fill - but usually not with marijuana

Travelers leaving from the Colorado Springs Airport have done a good job of stashing their marijuana at home or in their cars before they fly.

Amnesty boxes, which were added to the airport in January, have been sparsely used for marijuana, said Sgt. Matt Harrell of the Colorado Springs Department airport unit.

"I think people know," he said. "They haven't been trying it."

While some travelers have dropped off edibles, marijuana vapor cigarettes and grams of marijuana, he said those aren't the most common items.

"What we've gotten more than anything is unused prescription medication," Harrell said.

Since the 2012 passage of state Amendment 64, which allows people 21 years and older to use or have recreational marijuana, and the official implementation of the law in the state this year, agencies, organizations and law enforcement officials have had to adapt to the change.

With federal law prohibiting marijuana - and having jurisdiction over airplane travel - confusion can emerge where state laws differ.

The amnesty boxes give passengers a last chance to ditch anything that might be illegal before going through security and possibly facing consequences.

The Transportation Security Administration, which screens airlines passengers and their bags, will call Colorado Springs police if a passenger tries to take marijuana onto a plane.

Denver International Airport does not have marijuana amnesty boxes, a spokesman for the airport said. They ask people to just throw it away, he said.

In addition to marijuana and prescription drugs, Harrell said other items, such as water bottles and cigarette butts, are found when the boxes are checked once a month.

"Probably gummy bears are the strangest thing we've seen in there," he said.

Can you travel with?


1. Marijuana? No. Federal law prohibits passengers from traveling with marijuana, medical or recreational.

2. Prescription drugs? Yes. They can be checked or carried on to a plane. TSA recommends the medication is labeled to help get through security faster, but it is not required.

3. Ninja stars? Yes. Passengers can take martial arts and self defense items such as brass knuckles and ninja stars on a plane, but they must be checked in.

4. Nerf guns? Yes. TSA suggests you check them, though.

5. Snow globes? Yes. If it appears to contain less than 3.4 ounces of liquid it can be packed in carry-on luggage as long as it fits in a one-quart sized bag plastic bag. Larger snow globes must packed in checked bags.

6. Live fish? Yes. But as a carry-on only. The TSA says the fish must be in a clear, plastic spill-proof container, which may be more than 3.4 ounces. A TSA officer will have to visually inspect the fish.

7. Alcohol? Yes. Bottles of alcohol more than 3.4 ounces must be checked in. Bottles with less liquid may be carried on, but must be in a one quart/liter plastic bag with a zip-top and are limited to one per person.

8. Snakes? It depends. The TSA recommends you check airline policy before traveling with pets and animals. Some can be carried on or checked.

9. Frozen rack of lamb? Yes, meat, fish and vegetables and other food items can be checked and carried on. If the food is packed in ice, or ice packs, the ice must be frozen when taken through the screening. If not, they will not be allowed. The FAA limits a passenger to 5 pounds of dry ice, which can also be carried on or checked.

10. Crematory remains? It depends. Some airlines do not allow cremated remains as checked baggages. Security officials will not open the crematory container. TSA suggests a container made of lightweight material, like wood or plastic.

11. Spray paint? It depends. Chemicals such as chlorine, bleach, tear gas and spray paint are not allowed to be carried on. They may be allowed in checked bags. Passengers should check with their airlines.

Source: apps.tsa.dhs.gov/mytsa/cib_home.aspx

Read more at http://gazette.com


Casey Parker with Colorado Springs Airport Operations installs an amnesty box outside the security checkpoint at the airport Wednesday, January 15, 2013. Two amnesty boxes are being installed for people who didn't realize that it's illegal to possess marijuana on a plane. It is legal to leave marijuana in a parked car at airports under the Colorado law that legalized recreational marijuana, but you can't bring marijuana inside airport facilities. Photo by Mark Reis, The Gazette

Aviation authors to co-pilot event about northern flying life

Into the Abyss

By Carol Shaben

Random House

Polar Winds

by Danielle Metcalfe-Chenail


Dundurn Canadian authors Carol Shaben and Danielle Metcalfe-Chenail are women whose recent books delve into the world of aviation, small planes and the pilots who often risk their lives to pursue their passion. Shaben’s debut book — Into the Abyss — is a national bestseller, a B.C. Book Prize finalist and winner of Canada’s Edna Staebler award for creative non-fiction. Danielle Metcalfe-Chenail is Edmonton’s Historian Laureate and author of two books — For the Love of Flying and Polar Winds: A Century of Flying in the North. Both writers will be teaming up for the Vancouver launch of Polar Winds on Dec. 2.

Q Why did you each decide to write these books?


A My interest arose after my dad survived a small plane crash in northern Canada. I was 22 and working overseas when I found out about it reading a local newspaper. When I returned home months later, I saw that the tragedy had transfigured my dad. He’d seen six people die, including friends and a close colleague, and had struggled, along with three fellow survivors to stay alive until rescue came. He forged extraordinary bonds with these men, including a convicted criminal and the rookie pilot. I sought out that pilot almost 20 years later and it was he who educated me about the pressures and risks young pilots faced — and continue to face — flying for smaller commuter airlines. These airlines are a lifeline for Canadians in isolated communities both in B.C. and in Canada’s north. I started to investigate the industry and was shocked to discover that small plane safety is still a concern more than a quarter century later. That investigation morphed into an award-winning article, and later, my book. Danielle came to write about aviation through her fascination with the North. Whereas I grew up in northern Alberta, she was raised in southern Ontario, so had a curiosity about this vast region and its people. With her first book, she learned how aviation is an amazing window into Canada’s history and has been connected to almost every development in the North, from resource exploration to public health and even residential schools. In her second book she really draws on her background in social and cultural history to shine a light on the lived experiences of northerners in the air and on the ground, especially using the often hidden voices from women, indigenous peoples and visible minorities.

Q Tell me about the event on Dec. 2 in Vancouver.

 
A We’re calling it Turbulent Tales: The Ups and Downs of Writing About Canadian Aviation. It’s going to be a relaxed evening of conversation between Danielle and I about our research and writing journeys, and on the theme of aviation. We bring different backgrounds to the table, which will be really interesting. I’m someone who left a career to return to school for an MFA in creative writing, and then pursue investigative journalism and writing. Danielle is a historian who started out as a creative writer and is now trying to marry the two in rigorously researched popular history. Neither of us are pilots, but both feel we’ve been adopted into the aviation community. We also each had personal connections that led us to write the books we did. The event is open to the public and will take place at the Billy Bishop Legion in Kitsilano. There will be free refreshments, beverages for sale and, of course, we’ll be selling and signing books.

Q You’ve both chosen to write about aviation. Any thoughts on the theme?


A I think Danielle and I would agree that its astonishing how much has changed and how little has changed in over a century of flight in both northern Canada and when flying with smaller carriers. Pilots have gone from no navigation aids — no maps, or beacons and imprecise human systems such as dead reckoning — to GPS. They’ve gone from freezing open-cockpit planes they could only fly by visual contact with the ground (and no way to call for help), to planes with the latest instruments, safety features and communications technologies. And yet, any pilot flying into Canada’s northern or remote reaches will tell you that people and airplanes are still at the mercy of the weather and human error — be it from inadequate risk analysis or poor pilot decision making — and that these factors can still have surprisingly tragic results.

Turbulent Tales: The Ups and Downs of Writing About Canadian Aviation will take place Tuesday, Dec. 2 from 7 to 9 p.m. at the Billy Bishop Royal Canadian Legion, 1407 Laburnum St. The event is free and open to the public and light refreshments will be provided. Drinks will be available for purchase. Space is limited, so please RSVP by Sunday at info@daniellemc.com.

- Source:  http://www.thestarphoenix.com



Cirrus SR22T, N227RR: Accident occurred November 28, 2014 near Hampton-Varnville Airport (3J0), Hampton, South Carolina

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

Additional Participating Entities: 
Federal Aviation Administration / Flight Standards District Office; West Columbia, South Carolina
Continental Motors Inc; Mobile, Alabama 
Cirrus Design Corporation; Duluth, Minnesota 

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


Location: Hampton, SC
Accident Number: ERA15LA062
Date & Time: 11/28/2014, 1158 EST
Registration: N227RR
Aircraft: CIRRUS DESIGN CORP. SR22T
Aircraft Damage: Substantial
Defining Event: Loss of engine power (total)
Injuries: 1 Serious, 3 Minor
Flight Conducted Under: Part 91: General Aviation - Personal

Analysis

The private pilot was conducting a personal cross-country flight with three passengers on board. The pilot reported that, during the preflight inspection, he checked the quantity of engine oil and verified that there was an adequate supply of engine oil on board. During cruise flight, about 9,000 ft mean sea level (msl), the oil pressure indication decreased to 0, which resulted in both audible and visual warnings. The engine power then reduced to idle, and the pilot’s attempts to restore engine power by moving the throttle were not successful. The pilot subsequently diverted to a nearby airport about 7.5 nautical miles (nm) away. He stated that he descended the airplane slightly faster than the published best glide airspeed. When the airplane was at 800 ft msl and he realized it would not be able to land at the intended runway, he deployed the ballistic parachute. The airplane descended under the canopy, hit trees, descended to the ground, and then came to rest about 3/4 nm from the approach end of the intended runway. 

A postaccident examination and test run of the engine revealed no evidence of preimpact mechanical failures or malfunctions. Further, normal engine oil pressure was noted during the engine run; however, subsequent examination of the oil pressure transducer revealed that it was faulty and would have resulted in an erroneous oil pressure indication, as reported by the pilot. Further, although the pilot indicated that the engine lost power following the loss of oil pressure indication, which was supported by data downloaded from the onboard recording devices that showed decreased readings for fuel flow, exhaust gas temperature, and cylinder head temperature, the loss of engine power was consistent with the pilot’s operation of the engine controls not with a mechanical malfunction or failure of the engine. 

Although the pilot reported that he descended the airplane slightly above the published best glide speed after first locating the alternate airport, the recorded data indicated that he descended at an indicated airspeed far greater than the published best glide speed for the majority of the descent. If the pilot had slowed to and maintained the published best glide speed either at the time of the first abnormal indication or after first locating the alternate airport, it is likely that the airplane would have been able to reach the intended runway and land successfully. 

Further, although the pilot reported that he deployed the parachute at 800 ft msl, it was actually deployed when the airplane was at 453 ft msl, or about 340 ft above ground level (agl), excluding the treetop heights. Although the successful deployment of the parachute has been demonstrated at less than 400 ft agl, the low-altitude deployment likely contributed to the severity of the accident by not allowing the parachute to fully deploy and adequately decelerate the airplane into an approximately level attitude. 

Probable Cause and Findings

The National Transportation Safety Board determines the probable cause(s) of this accident to be:
The pilot’s improper decision to descend the airplane at an airspeed greater than the published best glide speed following an erroneous oil pressure indication, which resulted in an off-airport landing. Contributing to the erroneous oil pressure indication was the faulty oil pressure transducer. Contributing to the severity of the accident was the pilot’s late deployment of the ballistic parachute system.

Findings

Aircraft
Pressure - Malfunction (Factor)

Personnel issues
Decision making/judgment - Pilot (Cause)
Use of equip/system - Pilot (Cause)
Delayed action - Pilot (Factor)

Factual Information

On November 28, 2014, about 1158 eastern standard time, a Cirrus Design Corporation SR22T, N227RR, descended under the canopy of the Cirrus Airframe Parachute System (CAPS) and landed into a wooded area near Hampton-Varnville Airport (3J0), Hampton, South Carolina. The private pilot and two passengers sustained minor injuries, while one passenger sustained serious injuries. The airplane was substantially damaged. The airplane was registered to and operated by Header Bug LLC, under the provisions of 14 Code of Federal Regulations (CFR) Part 91 as a personal flight. Visual meteorological conditions prevailed at the time and an instrument flight rules flight plan was filed. The flight originated from Sarasota/Bradenton International Airport (SRQ), Sarasota, Florida, about 0933, and was destined for Orangeburg Municipal Airport (OGB), Orangeburg, South Carolina.

The pilot stated that after arrival at SRQ, the airplane was removed from the hangar and, as part of his preflight inspection, he checked the quantity of engine oil, which was indicating 8 quarts, or full. After engine start, he taxied to the run-up area, and while there performed an engine run-up using the checklist. It included a check of the magnetos at 1,700 rpm, and a check of the load on the alternators. When the checklist was completed he obtained his IFR clearance, and departed from runway 04.

After takeoff the flight proceeded towards the destination airport while remaining in contact with air traffic control. About 3 minutes after last checking the engine parameters, noting all engine parameters (specifically, oil temperature, oil pressure, and CHT) were in the green, or at 1153:02, the oil pressure indication first began to decrease from the steady state reading. The oil pressure decreased to zero over the next 2 seconds and was annunciated by an audible warning. The airplane at that time was at 9,000 feet mean sea level (msl), or 8,542 feet pressure altitude and was about 9.5 nautical miles and 168 degrees from 3J0. The pilot reported the engine power went to idle, and he did not hear any sounds from the engine, which was running smooth but was idled back. He reported he had no control over the power, and did not observe any oil or mist coming out of the engine and did not notice any smoke from the engine from oil getting onto a hot exhaust. He also reported he did not hear a change in sound from the propeller as if the propeller had changed pitch, and the propeller never stopped. The passenger in the right front seat read the display on the multi-function display (MFD) that the oil pressure displayed in the red showing 0 oil pressure. In addition, on the primary flight display (PFD) a red highlighted "WARNING" about the oil pressure displayed. He fully enrichened the mixture control and moved the throttle in an attempt to restore engine power but there was no response.

Using the on-board avionics he confirmed the nearest airport was 3J0, and declared an emergency with air traffic control, advising the controller at 1153:39, "…I got an oil pressure going haywire." The controller advised the pilot that 3J0 was the nearest airport and was located 7.9 miles from the aircraft's present position. The pilot informed the controller at 1154:09 that the airport was in sight; the airplane at that time was at 7,647 feet msl and was located about 7.5 nautical miles and 163 degrees from the approach end of runway 29 at 3J0. The controller then asked the pilot if he needed assistance on the ground at 3J0, and he indicated he did. The controller subsequently informed the pilot that emergency crews were on their way to 3J0.

The pilot reported that with the engine at idle, he descended at 98 knots, although the best glide speed was reported to be 88 knots. After realizing he was unable to land at 3J0, he informed the passengers to tighten their restraints (seatbelts and shoulder harnesses) before activating the CAPS. At 1157:36, the pilot informed the controller that he was "…inches from making this uh runway before I have to deploy this chute on here so." He indicated that he pulled the CAPS activation handle at 800 feet but could not recall the airspeed at chute pull. While under the canopy, the tail came down just as the airplane hit the trees. He attributed this to the altitude of deployment. A portion of a wing was knocked off and the tail was almost separated. The airplane descended to the ground, and he reported the contact was hard. He later indicated securing the fuel selector while on the ground.

The airplane came to rest in a wooded area about ¾ nautical mile and 110 degrees from the approach end of runway 29 at 3J0.

According to the individual involved with the recovery of the airplane, there were no obvious discrepancies noted with the engine, and no oil was observed inside the engine compartment. In the resting position of the airplane (slight nose low), a total of four quarts registered on the oil dipstick (actually called an oil gage rod and cap assembly, part number (P/N 656616-2); which was tightly secured. After the airplane was raised from the ground to a level attitude, no oil streaking or stains were noted on the bottom of the fuselage or airframe. In that position, the oil quantity registered slightly above the "8" mark on the oil gage rod cap assembly, which was full. A copy of the NTSB Record of Conversation with the individual is contained in the NTSB public docket.

Following recovery of the wreckage, an examination of it and the engine was performed by representatives of the airframe and engine manufacturer with NTSB oversight. The avionics that recorded and retained data were downloaded with NTSB permission by a representative of the airframe manufacturer. The downloaded data was then provided to the NTSB Vehicle Recorder Division. Examination the engine revealed the oil quantity was approximately 8 quarts and the oil was "like new." At the request of the NTSB investigator-in-charge, the oil pump cover was removed to inspect the oil pump; no discrepancies were noted. Crankshaft, camshaft, and valve train continuity was confirmed. Examination of the wiring associated with the oil pressure transducer revealed the connection at the transducer was properly connected and strain relief of the wire harness at the transducer was noted. Electrical continuity was confirmed from the plug at the transducer for the supply and output pins to the appropriate pins at the firewall connection; however, continuity was not confirmed for the ground pin at the transducer connector. No damage to the wiring harness was reported and the condition of each connector and pins were satisfactory. A portion of the wiring harness was removed for further examination of the ground connection related to the oil pressure transducer.

Examination of the throttle and mixture controls in the cockpit revealed the throttle was full forward and the mixture control was in a mid-range position between full rich and idle cut-off, which matched the positions at each respective control in the engine compartment. Examination of the engine controls in the engine compartment revealed they were properly secured and once documented, full, unrestricted stop-to-stop movement was observed by activation of the cockpit controls. Examination of the engine-driven fuel pump revealed the drive coupling was intact and fuel was noted in the flexible hose from the outlet of the pump to the fuel metering unit. No fuel was noted at the inlet to the fuel pump. Examination of the CAPS revealed the rear harness remained snubbed. The fuel selector was found in the off position. The engine was removed from the airplane for an attempted engine run at the manufacturer's facility. Additional items retained by NTSB included the oil pressure transducer, the Cirrus Recoverable Data Module (RDM), and the SanDisk 4GB SDHC Card from the Garmin G1000. Additional details concerning the airframe and engine examination results are contained in NTSB field notes or report from the engine manufacturer representative that are contained in the NTSB public docket.

At the engine manufacturer's facility, while in the presence of NTSB personnel, the engine was removed from the crate and impact damaged components were replaced. Additionally, the oil pump cover which had been previously removed was reinstalled with new silk thread. The engine was mounted in a test stand with a test club propeller installed and included the engine oil cooler, but did not include the accident oil pressure transducer. A flexible fluid carrying hose was attached to the outlet of the oil cooler (same location at the oil pressure transducer location) and connected directly to the test bench analog oil pressure gauge. During the initial run, an oil leak was noted at the oil pump. The engine was secured and the silk thread at the oil pump cover was repositioned. The oil pump cover was re-installed and the engine was started and found to operate normally. During the second engine run normal oil pressure and engine operation was noted. Examination of the retained electrical wiring associated with the oil pressure transducer revealed continuity of the ground from the plug at the oil pressure transducer to the bundled location also shared by the tachometer sensor, fuel flow sensor, and manifold pressure sensor. A copy of the NTSB report and report from the engine manufacturer's representative concerning the engine run and wiring harness examination are contained in the NTSB public docket.

Following the engine run, the oil pressure transducer was examined at the manufacturer's facility with FAA oversight. The transducer was marked in part with "12-635-004" which is the Cirrus part number (P/N), and "G1014" which indicates it was manufactured July 10, 2014. The examination began with a visual examination which confirmed the transducer did not appear damaged. The pressure port was not obstructed or damaged, and there was no damage on the connector and no signs of fretting on the pins. The transducer was then subjected to x-ray examination which revealed there was no evidence of a loose contact or damage inside the sensor. The transducer was then subjected to bench testing which involved applying up to 5 volts DC power and 150 PSIG. The transducer worked with no discrepancies and was subjected to a tap by a mallet which did not change the output voltage. The transducer was then subjected to a parametric test at specific pressures from 0-150 PSID and at specified test temperatures between -30.0 degrees Celsius to +100.0 degrees Celsius. The unit passed testing at all test temperatures and pressures up to testing at +100.0 degrees Celsius and 100 PSID, but failed the remainder of the pressure testing at that temperature. A copy of the report from the transducer manufacturer is contained in the NTSB public docket.

The specification for the oil pressure transducer identified as Cirrus Part Number (P/N) 12-635-004, indicated the input pressure range was 0 to 150 PSIG, and the operating temperature range was -30 degrees to +100 degrees Celsius. The expected vibration was 10 to 2000 Hz, and the expected operating life was 10 million full pressure cycles minimum.

A review of the maintenance records revealed the airplane was manufactured in September, 2014. Since manufacture, there was no record of any work performed to the oil pressure transducer or any reported discrepancy (excluding the accident flight) with the oil pressure indication. The engine oil and filter were noted to have been changed twice. The first occurred on November 14, 2014, at tachometer time of 31.40, and the second occurred on November 20, 2014, at tachometer time of 44.10. The airplane hour meter and flight meter were reported to be 62.7 and 51.7 hours, respectively. Excerpts of the maintenance entries are contained in the NTSB public docket.

According to the Maximum Glide Chart found in the Pilot's Operating Handbook and FAA Approved Airplane Flight Manual (POH/AFM), the best glide speed at gross weight is published to be 92 KIAS, resulting in a glide ratio of 8.6:1. Based on the location and altitude being flown when the pilot reported 3J0 was in sight (7,647feet msl), and subtracting the airport field elevation (113 feet), flying at the published best glide speed would have allowed a glide distance of approximately 10.6 nautical miles. The calculations did not take into account the affect of wind. Further review of the emergency procedures section of the POH/AFM revealed that it contained a section related to oil pressure warning and revealed the checklist items indicated that if the oil pressure was low to reduce power to minimum required for sustained flight and land as soon as possible. The amplification section of that checklist indicated that low oil pressure may be caused by a loss of a significant amount of its oil and engine failure may be imminent. The emergency procedures section for "Engine Failure In Flight" of the POH/AFM indicated to establish best glide speed, and then to trouble shoot to restore engine power.

Further review of the POH/AFM pertaining to the deployment characteristics of the CAPS indicated that about 8 seconds after deployment, the rear riser stub line would be cut and the airplane tail would drop down into its final approximately level attitude. The descent rate was expected to be less than 1,700 feet-per-minute with a lateral speed equal to the velocity of the surface winds. Chapter 10 of the POH/AFM related to the CAPS indicated that although no minimum altitude for deployment had been set, "A low altitude deployment increases the risk of injury or death and should avoided. If circumstances permit, it is advisable to activate the CAPS at or above 2,000 feet AGL." The POH/AFM also indicated that as a data point, altitude loss from level flight deployments had been demonstrated at less than 400 feet. Eight seconds after deployment, the rear riser snub line would be cut and the airplane tail would drop down into its final approximately level attitude. The ground impact was expected to be the equivalent to touchdown from a height of approximately 13 feet. Excerpts from the POH/AFM are contained in the NTSB public docket.

According to the NTSB Recorded Flight Data Specialist's Factual Report concerning the Recoverable Data Module (RDM), downloaded data recorded in 1 Hz increments began at 0931:00, and ended at 1158:20, which contained the takeoff to about 8 seconds after deployment of the CAPS. Further review of the downloaded data revealed normal engine indications were noted from acceleration for takeoff at 0933:01 until about 1153:01, at which time the oil pressure was recorded to be 57 PSI. One second later, or at 1153:02, the oil pressure was recorded to be 38 PSI, while at the same time the recorded readings for rpm, fuel flow and manifold pressure, which share the same ground connection as the oil pressure ground, remained about the same as the recorded values 1 second earlier. The oil pressure indication decreased to 0 at 1153:04, and remained at that value for the remainder of the recorded data. The data for rpm, fuel flow and manifold pressure at 1153:04, remained at or near the previous recorded values. For about 34 seconds after the oil pressure indication was first recorded to be zero, the pressure altitude remained nearly the same while the indicated airspeed decreased from 143 knots to 109 knots. During the same time frame, the manifold pressure and fuel flow readings decreased, but the engine rpm remained about the same value. Beginning about 1153:38, or about 34 seconds after the oil pressure indication was noted to be 0, the pressure altitude began to decrease with a corresponding increase in airspeed which attained the highest value of 148 knots about 2 minutes later; the airspeed remained above 140 knots until 1156:09. At this time the airspeed began to decrease with a continual decrease in pressure altitude. At 1158:00, or about 5 minutes since the oil pressure began to decrease, and about 13 seconds before the CAPS was deployed, the airspeed was first noted to be less than the published best glide speed value of 92 knots. The CAPS activation handle was noted to be pulled at 1158:13,

while the airplane was at 453 feet msl and 87 knots, or approximately 340 feet above ground level. A total of 7 seconds elapsed time between the CAPS deployment and the end of recorded data was noted; the last recorded airspeed and ground speed values were 42 and 29 knots, respectively. Closer review of the recorded data from the time when the oil pressure indication was noted to be 0 revealed the engine rpm was noted to remain nearly the same for the next 4 minutes 6 seconds, while the fuel flow and manifold pressure indications were noted to begin to decrease about 2 and 3 seconds after the no oil pressure indication, respectively, and continued to decrease. Thereafter, the exhaust gas temperature and cylinder head temperatures began to decrease. A copy of the NTSB Recorded Flight Data Report and downloaded data are contained in the NTSB public docket.

A search of the Federal Aviation Administration (FAA) Service Difficulty Report (SDR) data was performed using the base Cirrus part number for the transducer. The data indicated there were a total of 8 reports; none of which were the specific complete part number of the pressure transducer in the accident airplane model. Closer review of the 8 reports indicated a total of the 6 reports were specified to be the transducer for oil pressure. Of the 6 reports, only one indicated the oil pressure went to 0. In that instance, the report indicated the oil pressure transducer was found to be inoperative. A copy of the SDR is contained in the NTSB public docket.

Cirrus personnel reported that beginning in 2010, they noticed an increase in warranty claims and customer satisfaction survey results showed a high replacement rate for oil and manifold pressure transducers which are similar and used on SR20, SR22, SR22TN, and model SR22T aircraft. The identified issue was erratic indication, which was attributed to be associated with connectors (baffler connector and connector at the transducer). Subsequently in August 2012, Service Bulletin (SB) 2X-77-04 was introduced which specified replacement in part of the oil pressure transducer and installed strain relief at the connector of the oil pressure transducer, and also removed the baffler connector. The actions of the SB were incorporated into production aircraft including the accident airplane. Cirrus personnel reported that after issuance of the SB, the number of warranty claims decreased in 2013, but increased again in 2014 and 2015. Cirrus is currently investigating and evaluating possible product improvements.

History of Flight

Enroute-cruise
Miscellaneous/other
Loss of engine power (total) (Defining event)

Emergency descent
Miscellaneous/other

Landing-flare/touchdown
Hard landing

Pilot Information

Certificate: Private
Age: 71
Airplane Rating(s): 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 3 With Waivers/Limitations
Last FAA Medical Exam: 03/17/2014
Occupational Pilot: No
Last Flight Review or Equivalent: 10/20/2014
Flight Time:  300 hours (Total, all aircraft), 250 hours (Total, this make and model) 

Aircraft and Owner/Operator Information

Aircraft Make: CIRRUS DESIGN CORP.
Registration: N227RR
Model/Series: SR22T
Aircraft Category: Airplane
Year of Manufacture:
Amateur Built: No
Airworthiness Certificate: Normal
Serial Number: 0884
Landing Gear Type: Tricycle
Seats: 4
Date/Type of Last Inspection:
Certified Max Gross Wt.: 3600 lbs
Time Since Last Inspection:
Engines: 1 Reciprocating
Airframe Total Time: 62.7 Hours at time of accident
Engine Manufacturer: Teledyne Continental
ELT:  C126 installed, activated, did not aid in locating accident
Engine Model/Series: TSIO-550-K
Registered Owner: Header Bug LLC
Rated Power: 315 hp
Operator: Header Bug LLC
Operating Certificate(s) Held: None

Meteorological Information and Flight Plan

Conditions at Accident Site: Visual Conditions
Condition of Light: Day
Observation Facility, Elevation: BNL, 246 ft msl
Distance from Accident Site: 29 Nautical Miles
Observation Time: 1155 EST
Direction from Accident Site: 326°
Lowest Cloud Condition: Clear
Visibility:  
Lowest Ceiling: None
Visibility (RVR): 
Wind Speed/Gusts: 7 knots /
Turbulence Type Forecast/Actual: / Unknown
Wind Direction: 30°
Turbulence Severity Forecast/Actual: / Unknown
Altimeter Setting: 30.4 inches Hg
Temperature/Dew Point: 7°C / 3°C
Precipitation and Obscuration: No Obscuration; No Precipitation
Departure Point: Sarasota, FL (SRQ)
Type of Flight Plan Filed: IFR
Destination: Orangeburg, SC (OGB)
Type of Clearance: IFR
Departure Time: 0933 EST
Type of Airspace:

Airport Information

Airport: Hampton-Varnville (3J0)
Runway Surface Type: Asphalt
Airport Elevation: 113 ft
Runway Surface Condition:
Runway Used: 29
IFR Approach: None
Runway Length/Width: 3580 ft / 60 ft
VFR Approach/Landing: Forced Landing 

Wreckage and Impact Information

Crew Injuries: 1 Minor
Aircraft Damage: Substantial
Passenger Injuries: 1 Serious, 2 Minor
Aircraft Fire: None
Ground Injuries: N/A
Aircraft Explosion: None
Total Injuries: 1 Serious, 3 Minor

Latitude, Longitude: 32.860556, -81.061667

NTSB Identification: ERA15LA062
14 CFR Part 91: General Aviation
Accident occurred Friday, November 28, 2014 in Hampton, SC
Aircraft: CIRRUS DESIGN CORP. SR22T, registration: N227RR
Injuries: 1 Serious, 3 Minor.

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 28, 2014, about 1200 eastern standard time, a Cirrus Design Corporation SR22T, N227RR, descended under canopy of the cirrus airframe parachute system (CAPS) and landed into a wooded area near Hampton-Varnville Airport (3J0), Hampton, South Carolina. The private pilot and two passengers sustained minor injuries, while one passenger sustained serious injuries. The airplane was substantially damaged. The airplane was registered to and operated by Header Bug LLC, under the provisions of 14 Code of Federal Regulations (CFR) Part 91 as a personal flight. Visual meteorological conditions prevailed at the time and an instrument flight rules flight plan was filed. The flight originated from Sarasota/Bradenton International Airport (SRQ), Sarasota, Florida, about 0933 EST, and was destined for Orangeburg Municipal Airport (OGB), Orangeburg, South Carolina.

The pilot stated that the purpose of the accident flight was pleasure. He intended to fly to OGB, which was the half way mark of the flight; however, the ultimate destination was to an airport in Leesburg, Virginia. After arrival at SRQ the airplane was removed from the hangar and the fuel tanks were filled. He then performed a preflight inspection using the checklist. No fuel contamination was noted and the oil quantity was checked and found to indicate 8 quarts, or full. After engine start he taxied to the run-up area, and while there performed an engine run-up using the checklist. It included a check of the magnetos at 1,700 rpm, and checking the load of the alternators. When the checklist was completed he obtained his IFR clearance, and departed from runway 04.

After takeoff the flight proceeded towards the destination airport. The pilot further stated that he checked the engine parameters; noting all readings citing specifically (oil temperature, oil pressure, and CHT) were in the green. About 3 minutes later, while flying at 9,000 feet mean sea level with the mixture leaned to the mark and the engine between 65 and 70 percent power, or 2,400 rpm, he heard an audible warning that the oil pressure was zero. The airplane at that time was near Savannah, or about 50 to 60 miles from OGB. The engine power went to idle, and he did not hear any sounds from the engine which was running smooth but was idled back. He reported he had no control over the power, and did not observe any oil or mist coming out of the engine and did not notice any smoke from the engine from oil getting onto a hot exhaust. He also reported he did not hear a change in sound from the propeller as if the propeller had changed pitch, and the propeller never stopped. The passenger in the right front seat read the display on the multi-function display (MFD) that the oil pressure displayed in the red showing 0 oil pressure. In addition, on the primary flight display (PFD) a red highlighted "WARNING" about the oil pressure displayed. He fully enrichened the mixture control and moved the throttle in an attempt to restore engine power but there was no result. Using the on-board avionics he confirmed the nearest airport was 3J0, which ATC confirmed. The controller called to the 3J0 airport to inform personnel there of his situation, and he descended at 98 knots (best glide speed is 88 knots).

The pilot stated that after realizing he was unable to land at 3J0, he informed the passengers to tighten their restrains (seatbelts and shoulder harnesses) before activating the CAPS, and pulled the CAPS activation handle at 800 feet; he did not recall the airspeed at chute pull. He reported that the engine stayed at idle during the descent, and while under canopy, the tail came down just as the airplane hit the trees. He attributed this to the altitude of deployment. A portion of a wing was knocked off and the tail was almost separated. The airplane descended to the ground, and he reported the contact was hard.

The airplane came to rest about ¾ nautical mile and 110 degrees from the approach end of runway 29 at 3J0.

Preliminary inspection of the airplane revealed the right wing was fractured at the outboard end of the flap, and the empennage was fractured just forward of the leading edge of the horizontal stabilizer. The airplane was recovered for further examination.









VARNVILLE, S.C. (WJCL) — Officials confirmed that an airplane crashed, in Hampton County, S.C. on Friday. 

 According to the Associated Press, Hampton County Emergency Management Director Susanne Peeples said that the pilot reported an emergency before crashing around 1 p.m. Friday at the airport near Varnville.

In the accident, one was air-lifted after a plane crashed about a quarter mile short of the runway of the Hampton-Varnville Airport – about a mile outside of Varnville.

However, neither the one sent off by helicopter nor the other three suffered life-threatening injuries.

The Federal Aviation Administration (FAA) has been called in to investigate the accident and is on the scene with more expected to join the investigation.

The incident involved a Cirrus aircraft which had a airframe parachute system.


HAMPTON COUNTY, S.C. - A small aircraft has crashed just short of the airfield at the Hampton County airport in Varnville. Chief Deputy Billy Jarrell with the Hampton County Sheriff's Office says there were four people on board who sustained minor injuries, and were transported for treatment of the non life threatening injuries.

 Hampton County Emergency Management Director Susanne Peeples says the worst of the injuries sustained was a shoulder fracture. A woman who suffered the injury was transported from Hampton Regional to Charleston for treatment. The other three passengers are being treated at Hampton Regional. The passengers are from Virginia. Their names are not yet being released.

Peeples says that around 1:00 p.m., a distressed signal came from the plane as it went down. Fortunately, the plane had a parachute that deployed. Emergency crews say that without the parachute to lessen the crash, the incident could have been much worse.

Neighbor Kaitlin Alberson says she and her father heard and saw the plane crash.

"It was spitting and sputtering, and I looked outside up in the sky and we saw a plane and then a parachute came out, and then we heard this big crash like power blew out," Alberson says.

Alberson and her father arrived on the scene to see if any passengers needed help, shortly after first responders did. That's when Alberson snapped the photos featured in the article.

Neither Jarrell nor Peeples know what caused the plane to crash into the wooded area near the airport, off of Walterboro Highway and Papas Road. The Federal Aviation Administration (FAA) has been investigating the cause.

=====

HAMPTON CO., SC (WTOC) -  It was a frightening end to a holiday trip when a small plane went down in rural South Carolina.


Officials say it happened around 1 p.m. Friday in a wooded area off of Walterboro Highway in Varnville, SC.

EMS and Hampton Fire responded to the crash site and Lifestar was called to the scene.

The pilot reportedly made a distress call to air traffic control just before crashing a few miles away from the Hampton Varnville airport.

There were four people from Virginia on board the plane. Two men and one woman were taken to Hampton Regional Hospital with minor injuries. One other woman was airlifted with a shoulder injury just as a precautionary measure.

"We have a very fortunate situation. No one was seriously injured. We're very fortunate. This has been an experience for us. It isn't something that Hampton County has everyday. So we're very thankful that no one was hurt seriously and we hope the person that does have the worse of the injuries, that she will be okay," said Susanne Peeples, Hampton County EMA director.

Officials have not yet determined what caused the plane to crash.  The FAA continues to investigate.

Source:  http://www.wmcactionnews5.com

Hijack alert sees Turkish plane's jet escort

A Turkish Airlines pilot's mistaken activation of a hijack alarm triggered a high-octane security deployment at Vienna airport on Friday, Austrian police said.

The error -- coupled with a depressurization warning and then unexplained radio silence from the cockpit -- led to two jet fighters being scrambled to escort the Boeing 737 to land at Vienna's Schwechat airport.

The passenger plane had been flying from Frankfurt to Istanbul when panicked passengers saw oxygen masks fall from the ceiling after it was hit by a pressurization problem.

The pilot -- who had asked to make an emergency landing  -- apparently inadvertently activated the hijack alarm as he responded to the problem, police said, confirming a report on the website of the daily Kurier newspaper.

Authorities stepped down from their hijack alert status 40 minutes after the plane landed, Kurier said.

 
- Source:  http://www.thelocal.at

Boeing hopes SpiceJet's 'fleet reduction' strategy will work

NEW DELHI: With an order for 42 Boeing 737 Max worth $4.4 billion from crisis-ridden SpiceJet, the US aircraft major hopes that SpiceJet's strategy of "shrinking now and expanding later" - a reference to SpiceJet's ruthless fleet reduction - would work.

Boeing commercial airplanes (VP-sales) Dinesh Keskar was in India recently and told TOI that the delivery of 737 Max to SpiceJet, Boeing's answer to Airbus' hugely successful A320 Neo, begins from 2018 onwards and by then the low cost carrier (LCC) "will find a way out".

SpiceJet had ordered 42 Boeing 737 Max at the Hyderabad air show this March. But today, the LCC is struggling to survive by returning planes, cutting flights drastically and its auditors casting aspersion on its claim of being a going concern.

"I am not much worried. They will find a way. Their strategy is of shrinking now and expanding later. When you are hurting, the last thing you want to do is expand. Anyway, SpiceJet is supposed to start getting the Max from 2018 onwards," Keskar said. SpiceJet is today flying just 22 Boeing 737s - down from 35 in summer - and has cut over 50 daily flights reportedly due to a lack of funds that saw leasors taking back planes.

Asked won't the going get tougher for existing carriers, including SpiceJet, when Tata-Singapore Airlines JV airline starts flying soon and when Tata-AirAsia JV expands its wings, Keskar said: "Thanks to oil prices, airline operating costs have fallen. With those reduced costs and the current fare levels, the average gap in break-even price per ticket is just $10 (Rs 600-700). Indian carriers will be in profit during this peak holiday season." He added that SpiceJet will be able to deploy its smaller fleet more gainfully.While aircraft manufacturers keep their fingers crossed for airlines - remember the hit Airbus took when its customers Air Deccan and Kingfisher folded up with the latter having placed orders for five A-380s that were written off only recently - SpiceJet is fighting for survival. The directorate general of civil aviation (DGCA) has asked the LCC to give weekly status reports on its payables to various agencies.

Top DGCA officials say the airline has informed them that as many as 116 pilots have resigned and are serving notice period till mid-2015. While multiple top officials of DGCA confirmed getting this information from SpiceJet, the airline denied having giving any such information to the regulator when reached for comment.

On its part, SpiceJet says it is cutting Boeing fleet to get out of unfavorable leasing contracts. "We are revamping the fleet to come out stronger and shed unfavorable contracts and unwanted aircraft. We are doing this as part of turnaround process.... (Our) schedule reduction is about 50," Kapoor had told TOI last Sunday, while claiming that the airline's Boeing 737s fleet will grow to about 30 by the year-end.

- Source: http://timesofindia.indiatimes.com

Clutha helicopter crash report hit by delay: Eurocopter EC 135 T2+, G-SPAO

The final investigation report into the Clutha helicopter crash a year ago today will not be ­published until mid-2015.

A draft version will take several weeks to complete, the UK Department for Transport’s air accident investigation branch (AAIB) said yesterday. It will then be sent to “interested parties”, such as relatives of those who died and the helicopter firms involved, early next year.

Ten people were killed when a Police Scotland helicopter crashed on to the Clutha bar in Glasgow city center on Friday, 29 November, 2013.

The AAIB issued its last interim report into the crash in February, when it revealed the helicopter’s two engines had failed after being starved of fuel, despite 76kg of fuel remaining in its main tank.

The AAIB said the two fuel supply tanks linking the main tank to the engines were almost empty, but it found no problems with the connecting pipes.

It said yesterday the investigation had been protracted because the Eurocopter EC135 T2+ aircraft was not required to have flight data or cockpit voice recorders. It said: “As a result, significant work was required to extract and analyze the contents of non-volatile mem­ory from microchipped equipment known to record data.

“This, together with further examination of the aircraft and subsequent tests, has now been completed, to the extent that the investigation team may reach its conclusions.”

The AAIB said it had been working with the helicopter manufacturer, engine manufacturer, the European Aviation Safety Agency, the UK’s Civil Aviation Authority and the helicopter operator, along with other specialists, “to establish the causes and contributory ­factors that led to the accident”

Its February report said the investigation would “seek to determine why a situation arose that led to both the helicopter’s engines flaming out when 76kg of fuel remained in the fuel tank group”.

Pilot David Traill and his passengers, police officers Kirsty Nelis and Tony Collins, lost their lives. Those killed in the pub were John McGarrigle, Mark O’Prey, Gary Arthur, Colin Gibson, Robert Jenkins and Samuel McGhee. Some 32 people were taken initially to hospitals across the city. Joe Cusker was pulled from the wreckage alive but later died in hospital.

Law firm Irwin Mitchell, which represents relatives of those who died, called for the final report to be published sooner, and repeated its demand for an urgent review of helicopters below a certain weight being exempt from carrying “black box” equipment.

Elaine Russell, a partner in the firm, said: “We cannot overstate how important it is for the AAIB to get this publication out as soon as possible so that our clients can understand what led to the incident, as well as what should be done to ensure that no-one else faces the terrible ordeals they have endured.

“The middle of 2015 is simply too long to wait for the answers that are needed.”

Jim Morris, a partner in the firm’s aviation law team, said: “Current regulations on the fitting black box equipment exempt helicopters weighing less than 3,175kg from having to carry it, which, as this tragedy and the latest AAIB update demonstrates, can make the job for the accident investigators much more challenging and cause significant delays in finding out the cause of accidents.

“This in turn leads to delays in providing answers to the loved ones of those affected, as well as affecting whether lessons can be learned and measures implemented to improve flight safety.

“One year on, and all of our clients remain frustrated and desperate for answers regarding how this terrible tragedy ­happened.”

Story and Comments:  http://www.scotsman.com

http://www.aaib.gov.uk/publications/special_bulletins

http://www.aaib.gov.uk/publications/special_bulletins/eurocopter

Piper PA-24-250 Comanche, N5897P: Accident occurred November 28, 2014 near Andrews University Airpark (C20), Berrien Springs, Michigan

NTSB Identification: CEN15CA064 
Accident occurred Friday, November 28, 2014 in Berrien Springs, MI
Aircraft: PIPER PA 24-250, registration: N5897P

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



BERRIEN SPRINGS, MI — Rory Robinson was in his house in Berrien Springs late Friday morning when he heard something outside that didn't sound quite right.

"It sounded like a big snowplow, only louder," said Robinson, who lives in the 400 block of Bluff Street. "It sounded like a plane going through the trees."

A second after hearing the noise outside, power went out. That's when Robinson, a former pilot, knew something was wrong and went outside to investigate.

"We immediately lost power, it took down power lines," Robinson said. "That's when I went outside and saw the plane. It came over the river, it went right through the trees on the top of the river bank and stopped about six feet short of a house."

Robinson said that he didn't hear any engine noise prior to impact and he didn't observe any leaking fuel around the wreckage.

"That was my biggest concern, besides for the people on board," he said. "I don't know if they ran out of fuel or what. There was no fuel leaking around the crash. I think he was trying to make it to Andrews (Airpark) in Berrien. I had heard no engine noise."

The crumpled aircraft, a Piper PA-24 Comanche, had four people aboard.

Two people in the aircraft suffered serious injuries and two people suffered minor injuries, said Rick Smiedendorf, chief of the Berrien Springs Oronoko Township Police Department.

The aircraft was headed from Richmond, Ind., to the Andrews University Airpark for a family gathering in the Berrien Springs area, according to a news release issued late Friday afternoon from the Berrien Springs Oronoko Township Police Department.

The Piper Comanche was being piloted by Bryce Fisher of Richmond. He was in the plane with his his father, Dr. William Fisher of Richmond, who owned the plane and was acting as co-pilot.

Also aboard were William Fisher's wife, Barbara, and Bryce Fisher's girlfriend, Miritha Morales of DeKalb, Ill.

William Fisher and his wife, both 70, were seriously injured in the crash.

As of 3:15 p.m. Friday, the wreckage of the aircraft was being removed from the scene, Robinson said. Seeing one of the wings being loaded on to a trailer, he noticed that the aircraft's retractable landing gear did not appear to have been extended.

"It was a low-wing aircraft," Robinson said. "It did have retractable gear on it. The gear appeared to be still up."

This incident is still under investigation, Federal Aviation Administration spokesman Roland Herwig said.

Story, Comments and Photo Gallery:  http://www.mlive.com
 

 
A single-engine plane crashed Friday morning at 11:12 a.m. behind a home in the 400 block of North Bluff in Berrien Springs, according to Berrien County dispatch. 

 Police sent out a report that evening stating that the pilot of the plane was Bryce Fisher who was flying with three passengers.

The first passenger and co-pilot was his father, Dr. William Fisher, who owned the plane. The other passengers were Barbara Fisher, wife of Dr. Fisher and Miritha Morales, girlfriend of Bryce.

According to reports all by Morales are from Richmond, IN, she is from Dekalb, IL.

The passengers were out and walking around when responders arrived and the pilot was trapped in the plane and had to be extricated.

We were told all four occupants are now in the hospital. Two of them appear to be in serious condition. 


The FAA will be taking over the investigation.

We're told four homes in the neighborhood lost power because I&M had to cut lines in order to free up the plane to be removed.

None of the surrounding houses, however, were damaged by the plane which landed just five to six feet away from the nearest home, according to reports.

The plane was headed from Richmond, Indiana to Andrews for a family holiday function, we're told.

Story, Comments and Photo gallery:  http://www.wsbt.com


http://registry.faa.gov/N5897P