Wednesday, December 31, 2014

Police: You can be arrested for celebratory gunfire

 

JACKSONVILLE BEACH, Fla. — On New Year’s Eve, police are on the lookout for a serious problem: celebratory gunfire.

It is because like the old saying goes: "what goes up must come down." Police here in Jax Beach and across our area are encouraging people to keep the guns down.

New Year's Eve two years ago was rough for pilot Graham Hill. He and his girlfriend went up to get a bird's eye view of fireworks when he was struck in the head by a bullet.

"I let her know that we had been shot at -- and just as soon as I said that, blood starting running down my neck,” Hill said in a YouTube video.

Hill was one of the fortunate survivors -- and a prime example of why celebratory gunfire is a bad idea.

"People don't think. They just go outside and fire a gun into the air. Where's that bullet? The bullet has to come down somewhere," said Jacksonville Beach Police Department Cmdr. Mark Evans.

Indeed it does. That's why so many people get hurt this time of year. The group Shot Spotters tracked 11,508 celebratory gunfire incidents nationwide in the fourth quarter of 2013. About 1,100 of those occurred in the last six hours of the year.

Illegal fireworks are also something to watch for.

"It's all fun and games until somebody gets an eye poked out or has to end up in the hospital because they have burns on their hands," said tourist Tina Goldstrom.

Hill wasn't the only one struck Jan. 1, 2013. An 8 year-old boy was hit in the leg by a bullet. They're incidents everyone hopes to prevent this New Year’s Eve.

"It's serious stuff. You see it all the time. On Fourth of July and obviously New Year's. People get hurt," Goldstrom said.

Celebratory gunfire is not only dangerous, it's illegal. Anyone caught doing it will be arrested, with no exceptions.

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


January  2013:   JACKSONVILLE, Fla. (WTLV) - Pilot Graham Hill was just looking for a good view of the downtown fireworks when he took his girlfriend for a New Year's Eve flight over downtown Jacksonville. Instead, he was met by gunfire. 

 "We were just north of the football stadium, at 1,200 feet when there was a loud pop. ...And that's when I noticed the bullet hole. And so I let her know that we had been shot at, and just when I said that I felt blood running down my neck."

In a YouTube video, Hill says he handed the controls to his girlfriend when he realized he'd been shot in the head, and used his jacket to staunch the bleeding. They landed safely at Craig Field. And he appears to have taken the incident with a dose of good humor, even posting this X-ray as his Facebook profile photo.

Jacksonville pilot and flight instructor Chris Hughes, who has actually flown the plane that was hit, heard about the incident in an online pilots' forum.

"Shocked. It's not something you would expect to really run into flying over a city like Jacksonville."

Unfortunately, the problem of celebratory gunfire is not that rare in Jacksonville. An 8-year-old boy was shot in the foot, also on New Year's Eve. And as we reported at that time, Jacksonville police say they answered 259 calls for discharged firearms on that day alone.

"They know it is wrong, it is illegal, just like any other law that is broken, they are out there doing it, they know it is not right, they just think they are not going to get caught," JSO spokesperson Melissa Bujeda told First Coast News.

Chris Hughes still views the shooting as a freak occurrence. But he will tell his flight students that it's just one more thing for a pilot to be prepared for.

"At this point, yeah, I would probably warn them, if they're flying on New Year's Eve or any other major holiday when Americans like to shoot guns, then be careful. That's probably what I'd warn them."

This incident has of course gotten a lot of attention in aviation circles. But the folks we spoke to at the FAA say the chances of it happening again are almost infinitesimally small.

Story and Video:  http://www.ksdk.com

Stoddard-Hamilton GlaStar, N16XP: Accident occurred December 10, 2014 near Sheridan County Airport (KSHR), Wyoming

NTSB Identification: WPR15LA058
14 CFR Part 91: General Aviation
Accident occurred Wednesday, December 10, 2014 in Sheridan, WY
Aircraft: MCHOLLAND GLASTAR, registration: N16XP
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 December 10, 2014, about 1315 mountain standard time, an experimental McHolland Glastar amateur-built airplane, N16XP, was substantially damaged following impact with terrain after experiencing a loss of engine power during approach to landing to a private airstrip about 2 nautical miles south of the Sheridan County Airport (SHR), Sheridan, Wyoming. The private pilot, the registered owner and sole occupant of the airplane, was not injured. Visual meteorological conditions prevailed for the local flight, which was being operated in accordance with 14 Code of Federal Regulations Part 91, and a flight plan was not filed. The flight had departed the airstrip about 30 minutes prior to the accident. 

In a telephone conversation shortly after the accident with the National Transportation Safety Board investigator-in-charge , the pilot reported that he had taken off from the private airstrip located at his residence about 30 minutes prior to the accident, and that while in the traffic pattern for landing the engine started to lose power. The pilot stated that when he realized he was too fast on the approach, he tried to lose airspeed. The airplane subsequently impacted a fence that bordered the airstrip, which resulted in substantial damage to its left wing.

The airplane was recovered to a secured location for further examination.

http://registry.faa.gov/N16XP

FAA Flight Standards District Office: FAA Casper FSFO-04

Federal Aviation Administration Aurora facility fire damage shown in photos



 AURORA, Ill. (WLS) -- Flights grounded. People stranded. We've seen images from outside of the Aurora air traffic facility, now for the first time, a look inside at the damage that crippled air travel in late September.

The I-Team obtained dozens of photos form the FAA under the Freedom of Information Act. They detail the damage caused by an intentionally-set fire inside the building known as Chicago Center. Flames melted computer cables, data lines and hard drives.

The pictures appear to show the fire was not isolated to one part of the basement room that functions as the nerve center of the air traffic control facility. Instead, the damage occurred under false floors and up on computer racks. Ceiling lights were scorched and ash covered sensitive equipment.

In all, the FAA reports that 20 racks of equipment and 10 miles of cabling had to be replaced.

"This was an act of sabotage where someone willfully and knowingly damaged key infrastructure for our national airspace system," said FAA Administrator Michael Huerta on Oct. 3.

That "someone," the government says, is FAA contractor Brian Howard. He allegedly used his access and intimate knowledge of the facility to set the fire Sept. 26 in what his attorney describes as a failed suicide attempt.

Howard's attorney tells the I-Team:

"Brian regrets the act he took at the lowest moment of his life. This single act is not reflective of the many years of dedicated and devoted service he gave to his country." 

Howard is charged with one count of destruction of aircraft facilities and remains in federal custody.

Story and Video:  http://abc7chicago.com

Cessna 172S, VH-PFT: Fatal accident occurred December 29, 2014 near Port Arthur, southern Tasmania, Australia

The family of a pilot killed in a Tasmanian light plane crash have paid tribute to their relative as police confirm his body and that of a second man have been removed from the wreckage.

Sam Langford, 29, and passenger Tim Jones, 61, died on December 29 when the single-engine Cessna slammed nose-first into waters in the state's southeast near the Tasman Peninsula.

Recovery crews on Tuesday winched the damaged aircraft from the 90-metre seabed and brought it to Hobart by barge, with the men still in the cockpit.

In a brief statement on Wednesday, police said they had since been removed.

"Members of Tasmania Police forensics services processed the aircraft and recovered the bodies of the two men," the statement said.

On the same day, family and friends published notices in the Mercury newspaper.

"Forever in our hearts and thoughts, your drive and ambition will keep us going and looking skywards," Mr Langford's family wrote. "We will never forget your cheeky smile. Sam, we miss you."

The notices also sent "thoughts and sympathies" to Mr Jones's family.

He was taking photos of boats competing in the Sydney to Hobart yacht race when the crash happened.

The Australian Transport Safety Bureau has assessed the wreckage and police are preparing a report for the coroner



Officers on board PV Van Diemen work to recover the wreck of a light plane which crashed during the Sydney to Hobart race.



Efforts to retrieve a plane that crashed into the sea off Tasmania's south-east, killing both people on board, have been suspended due to problems with recovery equipment.

Attempts to winch the plane the 90 metres to the surface began last night but were suspended early this morning.

It is understood police had the wreckage of the plane almost to the surface when a rope holding it broke.

The plane plunged back into the ocean floor. Further sonar work will be needed to relocate its exact position and start the retrieval process again.

Sonar images have confirmed the bodies of the pilot Sam Langford, 29, and 61-year-old photographer Tim Jones are still inside the cockpit of the Cessna 172 which crashed off Cape Raoul on Monday evening.

The pair were covering the Sydney to Hobart Yacht Race when the accident happened.

On Wednesday the plane was discovered in about 90 metres of water off the Tasman Peninsular, south of Port Arthur.

But Acting Assistant Commissioner for Tasmania Police, Tony Cerritelli, said there had been technical difficulties with the equipment needed to reach the wreckage.

"The plane was located on a sandy bottom in that area [off the Tasman Peninsula] and two deceased people were unfortunately located in the cockpit," Mr Cerritelli said.

"We believe that those two people are the two missing people who went down with the Cessna earlier this week."

Once the wreckage has been brought to the surface it will be examined by experts to help determine the cause of the crash.

The crash investigation is being handled by the Australian Transport Safety Bureau (ATSB).

ATSB spokesman Joe Hattley said the bureau wanted to speak to anyone with any information about the crash.

"The ATSB would be interested in any information that anyone has in relation to the aircraft accident and we'd like anyone with information or photos or anything at all to contact the ATSB on 1800 020 616," he said.

A number of yachts diverted from the race to offer assistance after hearing a may day call that a plane had crashed.

Helsal III skipper John Davis said when crew members raised the alarm they immediately suspended racing and went into search-and-rescue mode.

Two tourists, who were watching the yacht race from nearby cliffs, reported seeing a plane flying "really low" in the area where the crash happened.

Airlines of Tasmania said it was devastated to receive the news of the death of its pilot Mr Langford and his passenger.

Managing director Shannon Wells said the airline staff were receiving all support possible as they came to grips with the loss of their colleague.

"Our thoughts and condolences extend to family and friends of Sam and Tim," Mr Wells said.

"Both men were highly regarded within their industries. We'll all be worse off without their presence.

"Tasmania Police, the Search and Rescue volunteers and competitors in the Sydney to Hobart yacht race, who did as much as they could to assist, have all done a tremendous job in very difficult and tragic circumstances."

Story and Photo:  https://au.news.yahoo.com

McDonnell Douglas Helicopters MD530FF (369FF), N530KK, registered to and operated by the Las Vegas Metropolitan Police Department: Accident occurred December 31, 2014 in Las Vegas, Nevada

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

Analysis

The commercial pilot was conducting a local public flight. He reported that, about 7 minutes into the flight, while the helicopter was orbiting over a fixed area, he noticed the engine and rotor rpm decrease. The pilot rolled the helicopter out of the orbit, and the engine and rotor rpm stabilized momentarily at 97%. The pilot then attempted to increase the engine and rotor rpm while turning the helicopter toward a nearby airport. During the maneuver, the engine and rotor rpm decreased rapidly. The pilot entered an autorotation and executed an emergency landing. The helicopter then landed hard, and the tail impacted the ground and separated from the airframe.

A postaccident examination of the airframe and the engine revealed no anomalies that would have precluded normal operation. During an engine test run, the engine produced rated power. Examination of the fuel system revealed no anomalies, and a fuel sample taken from the helicopter tested positive as jet fuel (Jet A). The reason for the loss of engine power could not be determined.

Probable Cause and Findings

The National Transportation Safety Board determines the probable cause(s) of this accident to be:
A total loss of engine power during cruise flight for reasons that could not be determined because postaccident examination and testing did not reveal any anomalies that would have precluded normal operation.

Findings
Not determined
Not determined - Unknown/Not determined (Cause)
Factual Information 

On December 31, 2014, about 1330, Pacific standard time, an MD Helicopter Inc. 369FF, N530KK, was substantially damaged during an emergency autorotation landing following a sudden loss of engine power in Las Vegas, Nevada. The two commercial pilots on board sustained serious injuries. The helicopter was registered to, and operated by, the Las Vegas Metropolitan Police Department as a public aircraft flight. Visual meteorological conditions prevailed, and no flight plan was filed. The local flight originated from North Las Vegas Airport (VGT), Las Vegas, at 1322.

The pilot reported that he had taken off with 64 gallons of fuel and was orbiting over a fixed location when he noticed a drop in engine and rotor revolutions per minute (rpm). The pilot then rolled the helicopter out of the orbit, and the engine and rotor rpm stabilized momentarily at 97%. The pilot attempted to increase the engine and rotor rpm while turning west towards the North Las Vegas Airport. During the maneuver, the engine and rotor rpm rapidly degraded. The pilot entered an autorotation, and executed an emergency landing. The helicopter touched down hard, the tail impacted the ground, and separated from the airframe.

The helicopter was examined on-scene by a Federal Aviation Administration (FAA) inspector. The inspector stated that he was only able to look at one side of the engine because of how the helicopter was positioned on the ground, and that he did not identify anything unusual. He checked the flight controls and reported that everything was connected. The helicopter was recovered to the Las Vegas Metro Police Department's hangar at the North Las Vegas Airport. Two FAA inspectors examined the helicopter on January 7, 2015, and reported that the engine outer combustion chamber, external fuel line connected to the fuel nozzle, and the fuel nozzle connection had sustained impact damage. Additionally, the engine fuel nozzle b-nut was "finger tight."

On January 14, 2015, representatives from MD Helicopters and Rolls-Royce examined the helicopter with oversight provided by a FAA inspector. The helicopter sustained substantial damage to the lower fuselage structure, aft fuselage section, tailboom and landing gear. There was no damage to the main structural members of the fuselage and the transmission/static mast support structure. The aft cabin was intact with no visible damage. The underside of the fuselage displayed damage to the belly skin and supporting interior structure with major damage to the aft landing gear fitting and center beam.

The top aft surface of the composite engine air fairing showed evidence of main rotor blade contact along with the tailboom. The tailboom was severed into two segments. The forward segment was still attached to the upper aft boom fairing. The vertical and horizontal stabilizer were both firmly attached to the aft segment. The vertical stabilizer's stinger was broken off and the vertical and horizontal stabilizers both displayed impact damage from ground contact. The aft portion of the left and right landing gear struts were broken and splayed outward resulting in the helicopter coming to rest on the lower fuselage structure.

Cyclic and collective control continuity was verified. Damage to the tail rotor controls corresponded with tailboom damage. The tail rotor blades exhibited impact damage with bent spars or tear to the blade skin. The main rotor blade damage varied in severity and included blades being bent, chordwise wrinkling, leading/trailing edge and tip cap damage. One blade was fractured at the inboard end just outboard of the root fitting. Drive system continuity was verified. The main rotor system hub assembly and components displayed typical damage from main rotor blades contacting the tailboom during the hard landing. There was visible damage to the hub upper and lower shoe, feather bearings, pitch change housings, and droop stops. Damage was consistent with the excessive blade flapping and lead-lag excursions of the main rotor from sudden stoppage at low rotor rpm without engine power.

The fuel cells were near full and there was no reported fuel spillage at the accident site. A vacuum check from the fuel inlet line at the fuel pump to the fuel shut off valve was satisfactorily completed. The fuel cells were drained using the maintenance fuel pump located in the fuel cell and the left fuel cell cover removed. The fuel cells appeared undamaged and the fuel removed looked visually clean. The maintenance fuel pump was removed and the fuel inlet ports and fuel tank sump was inspected. No contamination or blockage was found. Inspection of the fuel line plumbing and fittings did not identify any damage or discrepancies.

Visual inspection found the engine and related systems sustained only minimal external damage. There was visible impact damage to the engine's outer combustor case, fuel nozzle and fuel line. The fuel nozzle was cleaned just prior to the accident flight and the fuel line was reported loose at the accident site, however the fuel line also exhibited impact damage. The engine manufacturer reported that past experience has shown that b-nuts that are not fully torqued on the fuel nozzle may not affect normal engine operation, and that properly torqued b-nuts don't come loose under normal operating conditions.

There was no obvious evidence of fuel leakage in the engine area. Inspection of the engine mounts found the aft engine mount legs bent at the turn buckles. The left and right engine side mounts appeared undamaged. There were contact marks on the firewall from the engine driveshaft indicating movement of the engine during the crash sequence. With electrical power applied the engine trim switch (N2) was functional when tested. Some pneumatic and fuel line b-nuts had torque paint that was broken or misaligned. A check of air, fuel and oil lines found them to be at least hand tight. A check of the throttle and governor controls was completed with no discrepancies noted. The engine was removed from the airframe for further examination and testing.

Examination and functional testing of the engine was conducted on January 20, 2015 at Aeromaritime America Inc., located on Falcon Field in Mesa, Arizona. Representatives from the airframe and engine manufacturers were present and oversight was provided by a FAA inspector. The damaged outer combustion case, combustion liner and fuel nozzle were replaced with serviceable items. Except for the fuel line to the fuel nozzle and the fuel supply line at the fuel control, no other fuel or pneumatic lines were altered prior to the test cell run. The engine was run on the test cell and no operational discrepancies were noted, with the engine producing rated power. After the test cell run, a pneumatic leak check was performed on the pneumatic portion of the fuel control system. The scroll to Pc filter line was disconnected and 30 psi air pressure was applied to the Pc filter. A soap solution was used to check all fittings and lines in the system for leaks. The Pg accumulator line connection showed a formation of small air bubbles indicating a leak. The line was tightened with wrenches and the leak stopped. All the other lines were checked with a torque wrench and found to have 65 inch-pound or greater torque.

Two external fuel lines were examined by the NTSB investigator-in-charge, one line that had orange fire sleeve attached from end to end that connected the engine to the firewall, and the other, a black hose connecting the firewall to the fuel shut off valve. The fuel lines were examined visually using a borescope, and by sectioning the lines into segments. Additionally, the fuel filter was examined and found to be clear of debris. The examination of these items revealed that they were in very good functional condition with no anomalies identified.

A fuel sample was taken from the fuel line that runs between the firewall and the shutoff valve. The sample was a clear fluid with a petroleum odor and had a small amount of white particulate sediment. The sample was analyzed by a third party. The sample was examined using ASTM D2887 (Standard Test Method for Boiling Range Distribution of Petroleum Fractions by Gas Chromatography) to determine the type of fuel in the sample. The distillation results for this sample were consistent with jet fuel (Jet-A). In addition, the visible particulates were tested using ASTM D5185 (Standard Test Method for Multi-element Determination of Used and Unused Lubricating Oils and Base Oils by Inductively Coupled Plasma Atomic Emission Spectrometry (ICP-AES)). The results were sodium (Na) 82.8 mg/kg, zinc (Zn) 4.9 mg/kg, iron (Fe) 5.4 mg/kg, and magnesium (Mg) 6.7 mg/kg. The elements found are commonly occurring elements found in many things, including soil.

The most recent weight and balance was dated April 3, 2014, showed the helicopter empty weight as 1975.22 pounds. At the time of the accident the gross weight was calculated to be 2,810 lbs. It was determined that the helicopter had been operating within the published weight and balance limits. Maintenance records and a witness statement show that a 100-hour airframe and engine inspection had been completed on December 31st but had not been signed off as completed by maintenance personnel before the pilots took the helicopter.

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

Additional Participating Entities:
Federal Aviation Administration / Flight Standards District Office; Las Vegas, Nevada
Las Vegas Metropolitan Police Department; Las Vegas, Nevada
Rolls Royce; Indianapolis, Indiana
MD Helicopters; Mesa, Arizona

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

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

http://registry.faa.gov/N530KK

NTSB Identification: WPR15TA071
14 CFR Public Aircraft
Accident occurred Wednesday, December 31, 2014 in Las Vegas, NV
Aircraft: MD HELICOPTER INC 369FF, registration: N530KK
Injuries: 2 Serious.

NTSB investigators may not have traveled in support of this investigation and used data provided by various sources to prepare this public aircraft accident report.

On December 31, 2014, about 1330, Pacific standard time, an MD Helicopter Inc. 369FF, N530KK, was substantially damaged during an emergency autorotation landing following a sudden loss of engine power in Las Vegas, Nevada. The two commercial pilots on board sustained serious injuries. The helicopter was registered to, and operated by, the Las Vegas Metropolitan Police Department as a public aircraft flight. Visual meteorological conditions prevailed, and no flight plan was filed. The local flight originated from North Las Vegas Airport (VGT), Las Vegas, at 1322.

The pilot reported that he had taken off with 64 gallons of fuel and was orbiting over a fixed location when he noticed a drop in engine and rotor revolutions per minute (rpm). The pilot then rolled the helicopter out of the orbit, and the engine and rotor rpm stabilized momentarily at 97%. The pilot attempted to increase the engine and rotor rpm while turning west towards the North Las Vegas Airport. During the maneuver, the engine and rotor rpm rapidly degraded. The pilot entered an autorotation, and executed an emergency landing. The helicopter touched down hard, the tail impacted the ground, and separated from the airframe.

The helicopter was examined on-scene by a Federal Aviation Administration (FAA) inspector. The inspector stated that he was only able to look at one side of the engine because of how the helicopter was positioned on the ground, and that he did not identify anything unusual. He checked the flight controls and reported that everything was connected. The helicopter was recovered to the Las Vegas Metro Police Department's hangar at the North Las Vegas Airport. Two FAA inspectors examined the helicopter on January 7, 2015, and reported that the engine outer combustion chamber, external fuel line connected to the fuel nozzle, and the fuel nozzle connection had sustained impact damage. Additionally, the engine fuel nozzle b-nut was "finger tight."

On January 14, 2015, representatives from MD Helicopters and Rolls-Royce examined the helicopter with oversight provided by a FAA inspector. The helicopter sustained substantial damage to the lower fuselage structure, aft fuselage section, tailboom and landing gear. There was no damage to the main structural members of the fuselage and the transmission/static mast support structure. The aft cabin was intact with no visible damage. The underside of the fuselage displayed damage to the belly skin and supporting interior structure with major damage to the aft landing gear fitting and center beam.

The top aft surface of the composite engine air fairing showed evidence of main rotor blade contact along with the tailboom. The tailboom was severed into two segments. The forward segment was still attached to the upper aft boom fairing. The vertical and horizontal stabilizer were both firmly attached to the aft segment. The vertical stabilizer's stinger was broken off and the vertical and horizontal stabilizers both displayed impact damage from ground contact. The aft portion of the left and right landing gear struts were broken and splayed outward resulting in the helicopter coming to rest on the lower fuselage structure.

Cyclic and collective control continuity was verified. Damage to the tail rotor controls corresponded with tailboom damage. The tail rotor blades exhibited impact damage with bent spars or tear to the blade skin. The main rotor blade damage varied in severity and included blades being bent, chordwise wrinkling, leading/trailing edge and tip cap damage. One blade was fractured at the inboard end just outboard of the root fitting. Drive system continuity was verified. The main rotor system hub assembly and components displayed typical damage from main rotor blades contacting the tailboom during the hard landing. There was visible damage to the hub upper and lower shoe, feather bearings, pitch change housings, and droop stops. Damage was consistent with the excessive blade flapping and lead-lag excursions of the main rotor from sudden stoppage at low rotor rpm without engine power.

The fuel cells were near full and there was no reported fuel spillage at the accident site. A vacuum check from the fuel inlet line at the fuel pump to the fuel shut off valve was satisfactorily completed. The fuel cells were drained using the maintenance fuel pump located in the fuel cell and the left fuel cell cover removed. The fuel cells appeared undamaged and the fuel removed looked visually clean. The maintenance fuel pump was removed and the fuel inlet ports and fuel tank sump was inspected. No contamination or blockage was found. Inspection of the fuel line plumbing and fittings did not identify any damage or discrepancies.

Visual inspection found the engine and related systems sustained only minimal external damage. There was visible impact damage to the engine's outer combustor case, fuel nozzle and fuel line. The fuel nozzle was cleaned just prior to the accident flight and the fuel line was reported loose at the accident site, however the fuel line also exhibited impact damage. The engine manufacturer reported that past experience has shown that b-nuts that are not fully torqued on the fuel nozzle may not affect normal engine operation, and that properly torqued b-nuts don't come loose under normal operating conditions.

There was no obvious evidence of fuel leakage in the engine area. Inspection of the engine mounts found the aft engine mount legs bent at the turn buckles. The left and right engine side mounts appeared undamaged. There were contact marks on the firewall from the engine driveshaft indicating movement of the engine during the crash sequence. With electrical power applied the engine trim switch (N2) was functional when tested. Some pneumatic and fuel line b-nuts had torque paint that was broken or misaligned. A check of air, fuel and oil lines found them to be at least hand tight. A check of the throttle and governor controls was completed with no discrepancies noted. The engine was removed from the airframe for further examination and testing.

Examination and functional testing of the engine was conducted on January 20, 2015 at Aeromaritime America Inc., located on Falcon Field in Mesa, Arizona. Representatives from the airframe and engine manufacturers were present and oversight was provided by a FAA inspector. The damaged outer combustion case, combustion liner and fuel nozzle were replaced with serviceable items. Except for the fuel line to the fuel nozzle and the fuel supply line at the fuel control, no other fuel or pneumatic lines were altered prior to the test cell run. The engine was run on the test cell and no operational discrepancies were noted, with the engine producing rated power. After the test cell run, a pneumatic leak check was performed on the pneumatic portion of the fuel control system. The scroll to Pc filter line was disconnected and 30 psi air pressure was applied to the Pc filter. A soap solution was used to check all fittings and lines in the system for leaks. The Pg accumulator line connection showed a formation of small air bubbles indicating a leak. The line was tightened with wrenches and the leak stopped. All the other lines were checked with a torque wrench and found to have 65 inch-pound or greater torque.

Two external fuel lines were examined by the NTSB investigator-in-charge, one line that had orange fire sleeve attached from end to end that connected the engine to the firewall, and the other, a black hose connecting the firewall to the fuel shut off valve. The fuel lines were examined visually using a borescope, and by sectioning the lines into segments. Additionally, the fuel filter was examined and found to be clear of debris. The examination of these items revealed that they were in very good functional condition with no anomalies identified.

A fuel sample was taken from the fuel line that runs between the firewall and the shutoff valve. The sample was a clear fluid with a petroleum odor and had a small amount of white particulate sediment. The sample was analyzed by a third party. The sample was examined using ASTM D2887 (Standard Test Method for Boiling Range Distribution of Petroleum Fractions by Gas Chromatography) to determine the type of fuel in the sample. The distillation results for this sample were consistent with jet fuel (Jet-A). In addition, the visible particulates were tested using ASTM D5185 (Standard Test Method for Multi-element Determination of Used and Unused Lubricating Oils and Base Oils by Inductively Coupled Plasma Atomic Emission Spectrometry (ICP-AES)). The results were sodium (Na) 82.8 mg/kg, zinc (Zn) 4.9 mg/kg, iron (Fe) 5.4 mg/kg, and magnesium (Mg) 6.7 mg/kg. The elements found are commonly occurring elements found in many things, including soil.


The most recent weight and balance was dated April 3, 2014, showed the helicopter empty weight as 1975.22 pounds. At the time of the accident the gross weight was calculated to be 2,810 lbs. It was determined that the helicopter had been operating within the published weight and balance limits. Maintenance records and a witness statement show that a 100-hour airframe and engine inspection had been completed on December 31st but had not been signed off as completed by maintenance personnel before the pilots took the helicopter.

NTSB Identification: WPR15TA071
14 CFR Part 91: General Aviation
Accident occurred Wednesday, December 31, 2014 in Las Vegas, NV
Aircraft: MD HELICOPTER INC 369FF, registration: N530KK
Injuries: 2 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 public aircraft accident report.

On December 31, 2014, about 1330 Pacific standard time, an MD Helicopter Inc. 369FF, N530KK, was substantially damaged during an emergency autorotation following a sudden loss of engine power in Las Vegas, Nevada. The two commercial pilots on board sustained minor injuries. The helicopter was registered to, and operated by, the Las Vegas Metropolitan Police Department as a public-use flight. Visual meteorological conditions prevailed, and no flight plan was filed. The local flight originated from North Las Vegas Airport, Las Vegas, at 1322.

The pilot reported that he was orbiting when he noticed a drop in engine and rotor revolutions per minute (rpm). The pilot then rolled the helicopter out of the orbit, and the engine and rotor rpm stabilized momentarily at 97%. The pilot attempted to increase the engine and rotor rpm while turning west towards the North Las Vegas Airport. During the maneuver, the engine and rotor rpm rapidly degraded. The pilot entered an autorotation, and executed an emergency landing. The helicopter touched down hard, the tail impacted the ground, and separated from the airframe. 

  LAS VEGAS -- The officers involved in the emergency landing of a Metro helicopter on a residential street on New Year's Eve have have been identified as Officer David Callen and Officer Paul Lourenco. 

Officer Callen has been employed with the Metro since March 2000 and Officer Lourenco has been employed with the LVMPD since July 1997.

Both officers are pilots assigned to the Emergency Operations Bureau, Search and Rescue/Air Support Detail.

Both officers were treated for their injuries at the University Medical Center Trauma Center and were released the same evening. The officers are both experienced pilots, each having over 2,200 flight hours, and both are certified flight instructors.

An audio clip of the radio traffic of the incident accompanies this release.

An extensive review of each of the aircraft in the LVMPD fleet is currently underway. Initially, no LVMPD helicopters will be flying in regular service. Each of the aircraft will go through a detailed inspection and maintenance record check. At the conclusion of each inspection, the respective aircraft will be released back into service.

The six helicopters in Metro’s fleet include one Bell 407, three McDonnell Douglas 530-FF’s, and two Bell HH-1H’s. The aircraft involved in this incident was a McDonnell Douglas 530-FF. The department now has five operational helicopters in the fleet.

The investigation into this incident remains ongoing. The Federal Aviation Administration is taking the lead in the investigation.



LAS VEGAS -- A Metro Police helicopter crashed in a Las Vegas neighborhood Wednesday afternoon injuring two officers, police said.

The crash occurred at 1:30 p.m. at Bonanza Road and 21st Street. The helicopter went down in the street, according to Metro.

The officers were transported to University Medical Center, police said. The FAA reports that the injuries aren't believed to be life-threatening. No citizens were injured.

Motorists are advised to avoid the area. Bonanza Road is closed between Bruce Street and Eastern Avenue.

Metro purchased the new MD 530F helicopter in July 2010. The Las Vegas Metropolitan Police Air Support Unit began operation in 1969. The unit has 22 helicopter pilots.

The NTSB and the FAA are investigating.

Story, Comments, Video and Photo Gallery:   http://www.8newsnow.com



















Alaska aviation fatalities down sharply in 2014

Alaska Dispatch News 
By   Colleen Mondor
December 31, 2014


As 2014 comes to a close, the Alaska aviation community can breathe a collective sigh of relief over dramatically improved accident statistics for the year. According to the National Transportation Safety Board aviation database, through Dec. 25, 2014, there were a total of 74 aircraft accidents in the state, resulting in five fatalities. This is a marked change from 2013, when 35 lives were lost in 94 crashes.


Sifting through safety statistics is a common activity for aviation analysts, but while the data can reveal what happened in a certain place and time, it can only offer clues as to why.


Over the past 10 years, Alaska has suffered an average of 100 aircraft accidents a year, with a high of 127 in 2005 and the lowest number (74) coming this year. About 80 percent of crashes annually involve general aviation or noncommercial flights. Overall, 2013 was the worst year for fatalities since 1997.


As the dramatic difference between 2013 and 2014 makes clear, it is difficult to come away with any broad conclusions from a short period of data and gauging potential permanent improvements in Alaska flight safety statistics requires a longer view. Therefore, year-to-year variations must be considered, at best, with cautious optimism, as determining a reasonable trend is impossible from one year to the next.


"Five years is a reasonable amount of time for a trend," said NTSB Alaska Region Chief Clint Johnson.


This means that while 2013 serves as a tragic anomaly compared to previous years, 2014 could simply be another anomaly -- albeit a far more positive one.


“Dating back to the late 1990s, when I first joined the NTSB, our office was working about 130-140 accidents a year here,” says Johnson, “and there has been a gradual decline in the overall number of accidents. However, as we’ve seen recently, that positive trend can change in an instant.”  

By looking at a larger block of accident figures, the NTSB and Federal Aviation Administration, along with civilian groups like the Aircraft Owners and Pilots Association, Alaskan Aviation Safety Foundation, Alaska Airmen’s Association and others can determine the best ways to reduce accidents through more targeted education, enforcement action or technology advancements.

Just as changes to the bush mail bypass system in 2002 resulted in fewer air carriers and have been also credited with sharply reduced commercial accidents (from 321 in the 1990s to 191 in the the 2000s), there are other aspects of the Alaska aviation environment which have drawn the attention of safety advocates.

Earlier this year, the NTSB took the unusual step of issuing an urgent safety recommendation to the FAA concerning oversight of the “regulatory compliance and operational safety programs” of the parent company of the Ravn Alaska air group. The NTSB's concerns extended to all three of Ravn's partner air carriers: Frontier Flying Service, Era Aviation (not associated with Era Helicopters) and Hageland Aviation, which were collectively responsible for a string of accidents and incidents between 2012 and 2014 resulting in six fatalities.

Concerns about weather reporting resources continue to dominate discussions statewide and were highlighted last month in a comprehensive article at AOPA's website, “Alaska is a weather-poor state,” written by AOPA Regional Manager for Alaska Tom George.

Further, general aviation pilots in particular struggle with loss of control at low altitude, the cause of at least four accidents in 2013. Anchorage NTSB investigator Chris Shaver completed a video on this type of accident -- sometimes referred to as “moose stalls” -- that graphically illustrates its tragic outcome.

And in May, the Mat-Su Traffic Working Group announced significant changes to common traffic advisory frequencies to the areas north and west of Anchorage. As reported in Alaska Dispatch News, the group was formed after a series of midairs including one on July 30, 2011 near Amber Lake that killed the four occupants of a Cessna 180. The pilot and passenger of the second aircraft, a Cessna 206, survived. The two pilots were transmitting on different frequencies, each believing he was using the correct one for pilots flying in that area, and were unaware of each other's positions.

“Safety is always the FAA’s top priority and improving general aviation safety in Alaska has been one of the FAA's top priorities for more than a decade,” said Kerry Long, FAA Alaskan Regional Administrator, when asked to comment on 2014's aviation record.  “Since early 2000, we have generally seen a study (sic) reduction in accidents and today Alaskans are enjoying the safest period in the state’s aviation history.”

“Despite these successes, we’re not taking our eyes off our goal of achieving even greater levels of safety," he added. "It takes both government and industry working together in a collaborative way to continually raise the safety bar.”

As federal agencies and user groups compare 2013 and 2014 however, some answers will remain stubbornly elusive. One example of this is the July 2013 crash in Soldotna that took the lives of the pilot and all nine passengers and occurred in clear weather on a paved, maintained runway with an aircraft that suffered no contributing mechanical anomalies, according to the NTSB public docket. Addressing problematic pilot decision-making behind such a crash is a daunting, if not impossible, endeavor.

Ultimately, 2014 was a great year for Alaska flying and all those pilots who made thoughtful, conservative flight safety decisions in the past 12 months are to be commended. Their stories are missing from the statistical record, but are the most critical component to aviation’s continued success in the state. It would be a fine thing if the most negative aspects of the Bush pilot myth are finally being left behind by the state's 21st century aviators, but it’s too early to be anything but hopeful going into 2015.

- Original article can be found at: http://www.adn.com

Piper PA-46-350P Malibu Mirage, N228LL: Fatal accident occurred August 31, 2014 in Erie, Colorado

NTSB Identification: CEN14FA467
14 CFR Part 91: General Aviation
Accident occurred Sunday, August 31, 2014 in Erie, CO
Probable Cause Approval Date: 08/10/2016
Aircraft: PIPER PA 46 350P, registration: N228LL
Injuries: 5 Fatal.

NTSB investigators either traveled in support of this investigation or conducted a significant amount of investigative work without any travel, and used data obtained from various sources to prepare this aircraft accident report.

The private pilot was inbound to the airport, attempting to conduct a straight-in approach to runway 33. Due to the prevailing wind, traffic flow at the time of the pilot's arrival was on runway 15. Another airplane was departing the airport in the opposite direction and crossed in close proximity to the accident airplane. The departing traffic altered his course to the right to avoid the accident airplane while the accident airplane stayed on his final approach course. The two aircraft were in radio communication on the airport common traffic advisory frequency and were exercising see-and-avoid rules as required.

Witnesses reported that as the airplane continued down runway 33 for landing, they heard the power increase and observed the airplane make a left-hand turn to depart the runway in an attempted go-around. The airplane entered a left bank with a nose-high attitude, failed to gain altitude, and subsequently stalled and impacted terrain. It is likely the pilot did not maintain the necessary airspeed during the attempted go-around and exceeded the airplane's critical angle of attack. The investigation did not reveal why the pilot chose to conduct the approach with opposing traffic or why he attempted a landing with a tailwind, but this likely increased the pilot's workload during a critical phase of flight. 

The National Transportation Safety Board determines the probable cause(s) of this accident as follows:
The pilot's failure to maintain adequate airspeed and exceedance of the critical angle of attack during a go-around with a tailwind condition, which resulted in an aerodynamic stall. A contributing factor to the accident was the pilot's decision to continue the approach with opposing traffic.

HISTORY OF FLIGHT

On August 31, 2014 about 1150 mountain daylight time, a Piper Malibu PA-46-350P airplane, N228LL, was substantially damaged when the airplane impacted terrain near the Erie Municipal Airport (EIK), Erie, Colorado. The airplane was owned by The Real Estate School, LLC, Erie, Colorado and privately operated. The private pilot and four passengers on board were fatally injured. Visual meteorological conditions prevailed and no flight plan had been filed. The personal flight was conducted under the provisions of 14 Code of Federal Regulations Part 91. The flight originated at Centennial Airport (KAPA), Denver, Colorado.

Multiple witnesses located at and around EIK saw the accident airplane on final approach to runway 33 while another airplane was departing runway 15. Witnesses stated the two airplanes crossed in "close proximity." The airplane continued down runway 33 and they heard an increase in engine power "as if to go-around." A witness in the fixed-base operator's building described the airplane as being at a low altitude with full power, in a left bank with a nose-high attitude. Witnesses said it appeared the "airplane did not want to fly, it appeared to be in a stall," and "it did not accelerate or climb." The airplane continued in a "rapid descent" until impacting the terrain.

PERSONNEL INFORMATION

The pilot, age 67, held a private pilot certificate with an airplane single-engine land, airplane multi-engine land, and instrument airplane ratings. A third-class airman medical certificate was issued on June 30, 2014, with the limitation: must wear corrective lenses. The pilot reported on his most recent medical certificate application that he had accumulated 1,300 total flight hours, with 60 hours in the previous 6 months. The pilot's logbook was not located during the investigation.

AIRCRAFT INFORMATION

The airplane, manufactured in 1994, was a six-seat, low-wing, retractable-gear airplane, serial number 4622164, and was powered by a Lycoming Engines TIO-540 engine, rated at 350 horsepower. The engine drove a metal, 2-blade Hartzell HC-I2YR-1BF/F80 variable pitch propeller.

According to the airplane's logbooks, the most recent annual inspection was accomplished on December 4, 2013, at a Hobbs time of 2,808.8 hours. According to the airplane tachometer, the airframe's total time was 2,910.7 hours at the time of the accident.

Additionally, the airplane was equipped with two fuel tanks, which hold 61 gallons per tank, of which; 1 gallon is unusable for each tank. Refueling records obtained from a fuel vendor revealed that the airplane had been most recently refueled the morning of August 31, 2014, with 12.98 gallons of 100 low lead aviation fuel at their location at EIK. Additional fuel receipts from EIK were obtained, which showed that the airplane was refueled on August 15, 2014 with 73.54 gallons, on July 18, 2014 with 39.01 gallons, and on July 13, 2014 with 67.24 gallons.

METEOROLOGICAL INFORMATION

The closest official weather observation station is located at EIK. At 1135, an automated weather observation system (AWOS) reported wind from 160 degrees at 6 knots; visibility 10 miles; temperature 21 degrees Celsius (C); dew point 10 degrees C; and an altimeter reading of 29.95 inches of mercury.

AIRPORT INFORMATION

Erie Municipal Airport is a non-towered airport operating in Class-G airspace underneath of Class-B airspace. The airport is equipped with one runway. Runway 15/33 is 4,700 feet in length and 60-feet wide. The reported field elevation of the airport is 5,119 feet mean sea level.

WRECKAGE AND IMPACT INFORMATION

The aircraft impacted the edge of a culvert about 350 yards west of runway 33 at EIK. The initial impact point to the main wreckage was about 180 feet at a 300-degree heading. Several components of the aircraft; including the radar pod, forward baggage door and vertical stabilator with attached rudder surface, were located within the debris field west of the initial impact site. The main wreckage came to rest inverted, on a heading of approximately 158 degrees. 

The fuselage sustained crushing damage to its belly skins along most of its entire length. The engine and baggage compartment were partially separated from the forward fuselage pressure bulkhead assembly. The tail section completely separated from the aft section of the fuselage at the rear pressure bulkhead assembly but remained attached to the fuselage by control surface cables. 

The external fuselage skins exhibited wrinkling and creasing along both sides. The roof section was partially crushed inward near the right forward side window and emergency exit window. The emergency window was pushed inboard and partially separated from the window frame. The rear fuselage, in the area of the rear bulkhead section where the tail section separated, sustained extensive impact damage.

The main cabin area of the fuselage remained mostly intact. All six seats remained attached to the floor. Some of the seat bottom cushions were reportedly removed by first responders.

Continuity of the forward control cables was established. The primary aileron cables remained attached to both of their respective aileron quadrant assemblies. Both elevator control cables remained attached to their respective quadrant sectors. Both rudder cables remained attached to their respective rudder quadrant sector.

The fuel selector valve found to be in the "off" position. The cockpit fuel valve lever was also found in the "off" position. First responders reported to the National Transportation Safety Board (NTSB) that the fuel selector valve was placed into the "off" position during rescue activities.

The fuel gascolator bowl assembly was upside down when it was disassembled. The upper bowl housing exhibited a trace amount of fuel. The bowl did not contain any fuel, and was free of contaminates. The fuel filter assembly exhibited minor particles, but was otherwise mostly free of contamination. No evidence of any water contamination was observed.

The left wing remained attached to the fuselage. The wing sustained ground impact damage. Both the flap and aileron surfaces remained attached to the wing. The aileron cable assemblies remained attached to the aileron quadrant drive sector at the aileron surface. The flap actuator assembly was observed in the retracted position. The pushrod remained attached to the flap surface bellcrank assembly. The landing gear was observed in the retracted position.

The right wing remained attached to the fuselage although it was broken at the main spar. The wing sustained ground impact damage but was otherwise mostly intact. The wing exhibited a downward bow and was partially separated about 5 feet outboard of the fuselage. Both the flap and aileron surfaces remained attached to the wing. The aileron cable assemblies remained attached to the aileron quadrant drive sector at the aileron surface. The flap actuator assembly was observed in the retracted position. The flap interconnect pushrod separated at the flap drive idler arm assembly due to impact. The landing gear was observed in the retracted position.

The rear fuselage section sustained some ground impact damage and remained mostly intact up to the rear pressure bulkhead assembly. The horizontal tail section separated from the rear fuselage at the rear bulkhead and remained attached to the fuselage by control surface cables. The vertical surface, with attached rudder surface, separated from the rear fuselage and was located in the debris path near the initial ground impact area.

Visual continuity of the tail surface control cables was established. Both elevator control cables remained attached to the elevator sector assembly.

The rudder surface torque tube assembly separated where it attaches to the rudder sector control. The rudder sector control sustained impact damage and both rudder control cables remained attached to the rudder sector control.

One propeller blade was broken off mid span, with chord wise polishing and some lengthwise scratches. The second blade was relatively straight with leading edge and chord wise polishing. 

The engine was removed from the airframe and subsequently examined at the recovery facility. The examination of the engine revealed the sparkplugs appeared "worn out-normal" as compared to the Champion Aviation Check-a-Plug Chart AV-27. Both magnetos were rotated by hand and produced spark at all leads. The crankshaft was rotated by hand and compression was established at all cylinders. Engine drive train continuity was established throughout the engine crankcase. The cylinders were borescope inspected and no anomalies were noted. The oil pickup screen, oil filter and propeller governor screen were all found free of debris. The intake plenum was found crushed upward and cracked open. The left turbo charger was free to rotate but stiff; impact damage was noted. The right turbo charger was also free to rotate. The exhaust tubes were found crushed upwards. 

Fuel was noted in the fuel servo, lines, and flow divider. The flow divider diaphragm was found intact. The fuel injectors were found clear. Fuel was discharged from the engine driven fuel pump when rotated by hand.

No evidence of any preexisting mechanical malfunction that would have precluded normal operation of the airframe or engine was found.

MEDICAL AND PATHOLOGICAL INFORMATION

A post mortem examination was conducted under the authority of the Office of the Coroner, Weld County, Colorado on September 1, 2014. The cause of death for the pilot was attributed to multiple blunt force injuries.

The Federal Aviation Administration (FAA) Civil Aeromedical Institute performed toxicology examinations for the pilot which was negative for carbon monoxide, alcohol and drugs.

TESTS AND RESEARCH

The annunciator panel from the accident aircraft was removed by the NTSB Investigator-in-Charge (IIC) and sent to the NTSB Materials Laboratory, Washington, DC., to be examined for the presence of any stretched light bulb filaments. Stretched light bulb filaments are indicators the light bulb was illuminated at the time of the accident. Each annunciator light was x-rayed to determine the status of the two bulbs inside. No stretched filaments were found in any of the annunciator lights.

Additionally, an Apple iPad tablet computer was located within the wreckage. The tablet was subsequently sent to the NTSB Vehicle Recorder Division, Washington, DC. for further examination.

An exterior examination revealed the device had sustained extensive structural damage. The internal board was removed from the damaged device and installed in a surrogate iPad. The device was successfully powered on. However, the unit was protected by a 4-digit passcode and after possible passcodes were unsuccessfully tried, the device reported "iPad is disabled." No further recovery attempts were made.

For further information, see the Personal Electronic Device Report within the public docket for this accident.

OTHER INFORMATION

The NTSB's air traffic control (ATC) investigator reviewed radar data provided by the 84th Radar Evaluation Squadron (RADES) located at Hill Air Force Base in Utah. The radar data was recorded from the Denver ASR-9 (DEN).

There were no audio re-recordings available for this accident. According to radar data and witness statements, moments before the accident N228LL was on approach to runway 33 at EIK and passed in close proximity to N573MS who had departed runway 15 (opposite direction) at EIK. According to witness statements, the pilots of both aircraft were transmitting on the local common traffic advisory frequency (CTAF) which was not recorded (see witness statements in the public docket). Both aircraft were operating under visual flight rules (VFR) in visual meteorological conditions (VMC) and were not in communication with ATC while operating within class G airspace at an airport without an operating control tower.

Radar data indicated that the accident aircraft was inbound to runway 33 and was flying an approximately straight course to the runway with no observed significant deviations from that inbound heading. Radar data indicated that N573MS departed runway 15 at EIK and shortly after becoming airborne, made an abrupt deviation to the west (to the pilot's right).

According to radar data, the closest proximity between N228LL and N573MS occurred when the aircraft were separated by approximately 0.12 nautical miles (729 feet) laterally, and 200 feet vertically (and increasing). The flight track of N228LL indicated nothing out of the ordinary after passing N573MS, and it continued to approach EIK on course for runway 33 at a normal rate of descent. Witness statements indicated that N228LL appeared to be going around, however the aircraft never reached an altitude high enough for radar coverage and therefore any attempt at a go around was unable to be corroborated via recorded radar data.

According to the Piper Malibu Pilot's Operating Handbook, Section 4.33 Go-Around under Normal Procedures, states:

"To initiate a go-around from a landing approach, the mixture should be set to full RICH, the propeller control should be at full INCREASE, and the throttle should be advanced to full power while the pitch attitude is increased to obtain the balked landing speed of 80 knots-indicated airspeed (KIAS). Retract the landing gear and slowly retract the flaps when a positive climb is established. Allow the airplane to accelerate to the best angle of climb speed (81 KIAS) for obstacle clearance or to the best rate of climb speed (110 KIAS) if obstacles are not a factor. Reset the longitudinal trim as required."


Pilot Oliver Frascona, his girlfriend and her three children died in an August plane crash at Erie Municipal Airport.

Frascona, a prominent Erie real estate lawyer, was flying with 41-year-old Tori Rains-Wedan and her three children, according to the Weld County Coroner. Her children were 15-year-old Mason Wedan and 11-year-old twin brothers, Austin and Hunter. A dog also died in the crash.

Witnesses saw Frascona's Piper PA-46-350P Malibu Mirage sputtering and flying low to the ground, then a cloud of dust as it struck the ground.

First responders found the plane upside down.

Rains-Wedan was the owner of Educated Minds, which provides continuing education classes for real estate brokers. Mason attended Broomfield High School, while his brothers had started at Erie Middle School.

Read more:  http://www.coloradohometownweekly.com






 http://www.frascona.com




http://registry.faa.gov/N228LL
 
NTSB Identification: CEN14FA467
14 CFR Part 91: General Aviation
Accident occurred Sunday, August 31, 2014 in Erie, CO
Aircraft: PIPER PA 46 350P, registration: N228LL
Injuries: 5 Fatal.

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 either traveled in support of this investigation or conducted a significant amount of investigative work without any travel, and used data obtained from various sources to prepare this aircraft accident report.

On August 31, 2014 about 1150 mountain daylight time, a Piper Malibu PA-46, N228LL, was substantially damaged when the airplane impacted terrain near Erie Municipal Airport (EIK), Erie. The airplane was owned and operated by The Real Estate School, LLC, Erie, Colorado. The private pilot and four passengers on board were fatally injured. Visual meteorological conditions prevailed and no flight plan had been filed. The personal flight was conducted under the provisions of 14 Code of Federal Regulations Part 91.

In statements provided to the National Transportation Safety Board (NTSB) Investigator-In-Charge (IIC), witnesses saw the accident airplane on final approach to runway 33 while another airplane was departing runway 15. Witnesses stated the two airplanes crossed in "close proximity." The airplane continued down runway 33 and power was applied "as if to go-around." A witness in the fixed-base operator's building described the airplane at low altitude with full power, in a left bank with a nose-high attitude. Witnesses said it appeared the "airplane did not want to fly, it appeared to be in a stall," and "it did not accelerate or climb." The airplane continued in a "rapid descent" until impacting terrain.

At 1135, the EIK automated weather reporting facility reported wind from 160 degrees at 6 knots, visibility 10 miles, temperature 21 degrees Celsius (C), dew point 10 degrees C, and an altimeter reading of 29.95 inches of mercury.

The main wreckage contained all primary structural components and flight control surfaces. The wreckage was retained by the NTSB for further examination.


Federal Aviation Administration Flight Standards District Office: FAA Denver FSDO-03 


 
Oliver E. Frascona, Esq.