|37000 Feet||Browse and search NASA's
Aviation Safety Reporting System
|Local Time Of Day||0601 To 1200|
|Locale Reference||airport : w1o|
|Altitude||agl bound lower : 0|
agl bound upper : 0
|Controlling Facilities||tower : sfo|
|Operator||general aviation : personal|
|Make Model Name||Helicopter|
|Flight Phase||cruise other|
|Function||flight crew : single pilot|
|Qualification||pilot : commercial|
|Experience||flight time last 90 days : 100|
flight time total : 2200
flight time type : 90
|Qualification||other other : other|
|Anomaly||aircraft equipment problem : critical|
non adherence : far
|Independent Detector||other flight crewa|
|Resolutory Action||none taken : unable|
|Primary Problem||Flight Crew Human Performance|
|Air Traffic Incident||Pilot Deviation|
Helicopter was test flown by myself and an ai with the FBO. Flight appeared normal in all aspects. Aircraft was then flown again later in afternoon as a follow up flight. That evening I spoke with the ai with regards to the aircraft being released for flight and the annual inspection being signed of by him in the aircraft records. He assured me that the aircraft was released for flight and that he would have the entries made in the logbook later that day. I then assumed that since we did have his approval, the aircraft was legal to fly. Later that day, the aircraft had a hydraulic failure. The aircraft was landed west/O incident. It was later discovered that a plug in the hydraulic return line was left in the line. This caused pressure to build in the hydraulic system and the line to disconnect at the top of the transmission. Corrective action has been taken and it is now clear to me that an aircraft released for flight must have the proper entries in the logbook prior to any further flight after an annual inspection. There was no intent to fly an aircraft that was known to be unairworthy.
Original NASA ASRS Text
Title: HELI IS FLOWN AFTER ANNUAL BUT PAPERWORK HAD NOT BEEN COMPLETED. HYDRAULIC FAILURE RESULTED IN FORCED LNDG.
Narrative: HELI WAS TEST FLOWN BY MYSELF AND AN AI WITH THE FBO. FLT APPEARED NORMAL IN ALL ASPECTS. ACFT WAS THEN FLOWN AGAIN LATER IN AFTERNOON AS A FOLLOW UP FLT. THAT EVENING I SPOKE WITH THE AI WITH REGARDS TO THE ACFT BEING RELEASED FOR FLT AND THE ANNUAL INSPECTION BEING SIGNED OF BY HIM IN THE ACFT RECORDS. HE ASSURED ME THAT THE ACFT WAS RELEASED FOR FLT AND THAT HE WOULD HAVE THE ENTRIES MADE IN THE LOGBOOK LATER THAT DAY. I THEN ASSUMED THAT SINCE WE DID HAVE HIS APPROVAL, THE ACFT WAS LEGAL TO FLY. LATER THAT DAY, THE ACFT HAD A HYD FAILURE. THE ACFT WAS LANDED W/O INCIDENT. IT WAS LATER DISCOVERED THAT A PLUG IN THE HYD RETURN LINE WAS LEFT IN THE LINE. THIS CAUSED PRESSURE TO BUILD IN THE HYD SYS AND THE LINE TO DISCONNECT AT THE TOP OF THE XMISSION. CORRECTIVE ACTION HAS BEEN TAKEN AND IT IS NOW CLEAR TO ME THAT AN ACFT RELEASED FOR FLT MUST HAVE THE PROPER ENTRIES IN THE LOGBOOK PRIOR TO ANY FURTHER FLT AFTER AN ANNUAL INSPECTION. THERE WAS NO INTENT TO FLY AN ACFT THAT WAS KNOWN TO BE UNAIRWORTHY.
Data retrieved from NASA's ASRS site as of August 2007 and automatically converted to unabbreviated mixed upper/lowercase text. This report is for informational purposes with no guarantee of accuracy. See NASA's ASRS site for official report.