37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 300762 |
Time | |
Date | 199504 |
Day | Sat |
Local Time Of Day | 1801 To 2400 |
Place | |
Locale Reference | atc facility : kbv |
State Reference | FO |
Altitude | msl bound lower : 31000 msl bound upper : 31000 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | artcc : txkf |
Operator | common carrier : air carrier |
Make Model Name | B727-200 |
Operating Under FAR Part | Part 121 |
Navigation In Use | Other |
Flight Phase | cruise other other |
Route In Use | enroute : other oceanic enroute : atlantic |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
Qualification | pilot : commercial pilot : atp |
Experience | flight time last 90 days : 225 flight time total : 20000 flight time type : 10000 |
ASRS Report | 300762 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : first officer |
Qualification | pilot : instrument pilot : commercial |
Events | |
Anomaly | aircraft equipment problem : less severe other anomaly other other spatial deviation |
Independent Detector | aircraft equipment other aircraft equipment : unspecified other flight crewa |
Resolutory Action | flight crew : overcame equipment problem flight crew : returned to intended course or assigned course flight crew : became reoriented flight crew : declared emergency |
Consequence | Other |
Supplementary | |
Primary Problem | Aircraft |
Narrative:
Dispatched with 1 omega inoperative: I am writing this report because I disagree with the waiver allowed to air carrier's to operate caribbean rtes with 1 long range navigation system inoperative, and to point out that my air carrier's avionic maintenance is very poor. The basis of this waiver, apparently, is that flts are not out of radar coverage longer than 2 hours, and dead reckoning can be used with the computer flight plan information, ie mh, forecast wind, time fix, etc. Shortly after takeoff antigua, flight was rerted due to waters agreement from A312/523 to A632. #2 omega failed about 20 mins after losing radar contact with ZSU. Reported navigation equipment failure to ny and declared navigation emergency to land bda. The flight plan in this case was pretty much useless for dr navigation, as check points, course, magnetic heading, did not apply. As the failure occurred on the southern edge of a west to east jet stream (150 at core), we made heading adjustment similar to flight plan crosswind track correction of additional 10 degree longitude, right drift. At the bermuda fir, 45 mins later, aircraft was 40 mi east of course. In the meantime, did some trouble shooting and restored power to #2 omega. Accomplished precision updates at bda and targa and continued flight normally. Maintenance write up declared the aircraft unsafe for further flight over water without repairing both navigation system and flight checking same over land. Following day, we were assigned same aircraft to fly same trip, #1 omega still inoperative, #2 omega signed off 'suspect cause of power loss in rpu, replaced, checked ok on taxi during reposition from hangar.' since we were the last crew to fly the aircraft, we found it unusual that our maintenance gripe of #2 omega was not in the front of the logbook. In fact, it was placed in a pouch slightly out of order so that it would not appear to be from previous day flying. A new crew (unsuspecting) could have very easily missed my notation of a need to flight check omegas. Refused aircraft for overwater flight until flight checked!
Original NASA ASRS Text
Title: NAV EMER DECLARED AFTER THE LOSS OF THE SECOND OMEGA.
Narrative: DISPATCHED WITH 1 OMEGA INOP: I AM WRITING THIS RPT BECAUSE I DISAGREE WITH THE WAIVER ALLOWED TO ACR'S TO OPERATE CARIBBEAN RTES WITH 1 LONG RANGE NAV SYS INOP, AND TO POINT OUT THAT MY ACR'S AVIONIC MAINT IS VERY POOR. THE BASIS OF THIS WAIVER, APPARENTLY, IS THAT FLTS ARE NOT OUT OF RADAR COVERAGE LONGER THAN 2 HRS, AND DEAD RECKONING CAN BE USED WITH THE COMPUTER FLT PLAN INFO, IE MH, FORECAST WIND, TIME FIX, ETC. SHORTLY AFTER TKOF ANTIGUA, FLT WAS RERTED DUE TO WATERS AGREEMENT FROM A312/523 TO A632. #2 OMEGA FAILED ABOUT 20 MINS AFTER LOSING RADAR CONTACT WITH ZSU. RPTED NAV EQUIP FAILURE TO NY AND DECLARED NAV EMER TO LAND BDA. THE FLT PLAN IN THIS CASE WAS PRETTY MUCH USELESS FOR DR NAV, AS CHK POINTS, COURSE, MAGNETIC HDG, DID NOT APPLY. AS THE FAILURE OCCURRED ON THE SOUTHERN EDGE OF A W TO E JET STREAM (150 AT CORE), WE MADE HDG ADJUSTMENT SIMILAR TO FLT PLAN XWIND TRACK CORRECTION OF ADDITIONAL 10 DEG LONGITUDE, R DRIFT. AT THE BERMUDA FIR, 45 MINS LATER, ACFT WAS 40 MI E OF COURSE. IN THE MEANTIME, DID SOME TROUBLE SHOOTING AND RESTORED PWR TO #2 OMEGA. ACCOMPLISHED PRECISION UPDATES AT BDA AND TARGA AND CONTINUED FLT NORMALLY. MAINT WRITE UP DECLARED THE ACFT UNSAFE FOR FURTHER FLT OVER WATER WITHOUT REPAIRING BOTH NAV SYS AND FLT CHKING SAME OVER LAND. FOLLOWING DAY, WE WERE ASSIGNED SAME ACFT TO FLY SAME TRIP, #1 OMEGA STILL INOP, #2 OMEGA SIGNED OFF 'SUSPECT CAUSE OF PWR LOSS IN RPU, REPLACED, CHKED OK ON TAXI DURING REPOSITION FROM HANGAR.' SINCE WE WERE THE LAST CREW TO FLY THE ACFT, WE FOUND IT UNUSUAL THAT OUR MAINT GRIPE OF #2 OMEGA WAS NOT IN THE FRONT OF THE LOGBOOK. IN FACT, IT WAS PLACED IN A POUCH SLIGHTLY OUT OF ORDER SO THAT IT WOULD NOT APPEAR TO BE FROM PREVIOUS DAY FLYING. A NEW CREW (UNSUSPECTING) COULD HAVE VERY EASILY MISSED MY NOTATION OF A NEED TO FLT CHK OMEGAS. REFUSED ACFT FOR OVERWATER FLT UNTIL FLT CHKED!
Data retrieved from NASA's ASRS site as of July 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.