NTSB REPORTS

[rotowing]

Like to find out why a crash is not posted on the NTSB reports. Eagle Aviation in Ozark Al. crashed a UH-1 before Christmas, totaling the aircraft and it has never been posted on the NTSB. Thought that all crashes are posted regardless when , where, or why!!!

[rodrop]

There must be a reason, because I actually have tried to track down a heli crash and can't find it either..maybe it takes awhile to get ont he data base or at least shared online.

[67november]

on average NTSB reports take about a year to be published, so the only thing that should be available is the initial FAA report.

[Spike]

Like to find out why a crash is not posted on the NTSB reports. Eagle Aviation in Ozark Al. crashed a UH-1 before Christmas, totaling the aircraft and it has never been posted on the NTSB. Thought that all crashes are posted regardless when , where, or why!!!

 

I believe, "Public Use" accidents are not always posted.

[rotowing]

I believe, "Public Use" accidents are not always posted.

This was not a Public use helicopter, it was owned by the FBO there and flew by their pilot.

[PhotoFlyer]

It's possible they didn't report it.

[rotowing]

So if they did not report it would that be a violation , does it not say an accident doing major damage to aircraft be reported?

[PhotoFlyer]

Yes, it does say they must be reported, however, not every person out there is completely honest. There are people in aviation who would fail to report, and cover up, an accident if it was possible.

 

Rules are rules, and should be followed, but a book never kept anybody from breaking the rules.

 

To put it another way, armed robbery is against the rules, but it still happens with alarming regularity.

[Gomer Pylot]

The NTSB doesn't investigate every Part 91 accident. If it was Part 91, and nobody was killed, it's not necessarily investigated or published.

[rotowing]

So if it's not investigated by the NTSB it want show up as a crash on the pilots record is that correct?

Edited March 8, 2010 by rotowing

[rotorwish]

Sometimes these things take time to be found out. For example (Just skip to the end after viewing the date)

 

On March 26, 2005, about 0830 Pacific standard time, a Robinson Helicopter Company (RHC) R22 Beta, N820SH, impacted terrain following a loss of engine power during a practice autorotation near Los Banos, California. Silver State Helicopters, LLC., North Las Vegas, Nevada, operated the helicopter as an instructional flight under the provisions of 14 CFR Part 91. The flight instructor and the commercial pilot student were not injured. The helicopter was substantially damaged. Visual meteorological conditions prevailed, and a flight plan was not filed for the cross-country flight that originated from Los Banos around 0800. The flight was destined for Gustine, California.

 

The instructor pilot reported that shortly after departing Los Banos, he simulated a loss of engine power. The student, who was studying to become a flight instructor, initiated an autorotation to a field. When the instructor attempted to apply engine power following the practice autorotation, the engine "immediately quit." The instructor applied full collective to cushion the landing, but the helicopter landed hard in the field, structurally damaging the tail boom and the fuselage.

 

Following the accident, the operator returned the helicopter to their facility and test ran the engine. No anomalies were noted, and they believed the conditions were suitable for the development of carburetor ice during the autorotation. Review of archived weather data for the day of the accident revealed the weather observation facility at the Merced Municipal Airport, which is 24 miles northeast of the accident site, reported the temperature and dew point as 6 and 5 degrees Celsius, respectively. Plotting of those temperatures on a carburetor icing probability chart revealed that conditions likely existed for serious icing at any power setting.

The accident was reported to the Federal Aviation Administration's (FAA) Fresno Flight Standards District Office on August 23, 2005. FAA personnel informed the National Transportation Safety Board of the event on August 24, 2005