An A320 crew reports that because no NDB receiver is installed in this aircraft type; they could not...

Attributes
ACN	650945
Time
Date	200503
Local Time Of Day	0601 To 1200
Place
Locale Reference	airport : rno.airport
State Reference	NV
Altitude	agl single value : 0
Environment
Flight Conditions	VMC
Aircraft 1
Operator	common carrier : air carrier
Make Model Name	A320
Operating Under FAR Part	Part 121
Navigation In Use	other
Flight Phase	ground : preflight ground : parked
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Experience	flight time last 90 days : 125 flight time total : 8200 flight time type : 125
ASRS Report	650945
Person 2
Affiliation	company : air carrier
Function	flight crew : first officer
Events
Anomaly	aircraft equipment problem : critical non adherence : clearance non adherence : published procedure other anomaly other
Independent Detector	other flight crewa
Resolutory Action	none taken : unable
Supplementary
Problem Areas	Aircraft
Primary Problem	Aircraft

Narrative:

During preflight preparation while reviewing the engine out procedure for departing runway 16R; I discovered what seems to be a loophole in the engine out procedure for airbus aircraft that are equipped with GPS. In the event of an engine failure before flap retraction; the procedure calls for a left turn back to the 'no' compass locator (NDB). However; the airbus aircraft that have GPS installed do not have ADF receivers installed which are required to navigation to an NDB. There is a note on the engine failure procedure page that if an engine failure occurs before flap retraction then an eosid will automatically appear that may be inserted and followed; but only if you are on the 'FMG5' SID; which we were not -- we were assigned the 'wagge' SID. Therefore; our only options to navigation to the 'no' NDB was to try and type it in the mcdu as a fix to proceed direct to (which I'm not sure would really work) or if VFR conditions prevail (which in our case it was VFR) use pilotage and dead reckoning to navigation to the NDB which could be very difficult with an engine out scenario. This needs to be looked into and clarified or corrected.

Original NASA ASRS Text

Title: AN A320 CREW RPTS THAT BECAUSE NO NDB RECEIVER IS INSTALLED IN THIS ACFT TYPE; THEY COULD NOT COMPLY WITH AN ENG OUT PROC AT RNO REQUIRING NAV TO AN NDB.

Narrative: DURING PREFLT PREPARATION WHILE REVIEWING THE ENG OUT PROC FOR DEPARTING RWY 16R; I DISCOVERED WHAT SEEMS TO BE A LOOPHOLE IN THE ENG OUT PROC FOR AIRBUS ACFT THAT ARE EQUIPPED WITH GPS. IN THE EVENT OF AN ENG FAILURE BEFORE FLAP RETRACTION; THE PROC CALLS FOR A L TURN BACK TO THE 'NO' COMPASS LOCATOR (NDB). HOWEVER; THE AIRBUS ACFT THAT HAVE GPS INSTALLED DO NOT HAVE ADF RECEIVERS INSTALLED WHICH ARE REQUIRED TO NAV TO AN NDB. THERE IS A NOTE ON THE ENG FAILURE PROC PAGE THAT IF AN ENG FAILURE OCCURS BEFORE FLAP RETRACTION THEN AN EOSID WILL AUTOMATICALLY APPEAR THAT MAY BE INSERTED AND FOLLOWED; BUT ONLY IF YOU ARE ON THE 'FMG5' SID; WHICH WE WERE NOT -- WE WERE ASSIGNED THE 'WAGGE' SID. THEREFORE; OUR ONLY OPTIONS TO NAV TO THE 'NO' NDB WAS TO TRY AND TYPE IT IN THE MCDU AS A FIX TO PROCEED DIRECT TO (WHICH I'M NOT SURE WOULD REALLY WORK) OR IF VFR CONDITIONS PREVAIL (WHICH IN OUR CASE IT WAS VFR) USE PILOTAGE AND DEAD RECKONING TO NAV TO THE NDB WHICH COULD BE VERY DIFFICULT WITH AN ENG OUT SCENARIO. THIS NEEDS TO BE LOOKED INTO AND CLARIFIED OR CORRECTED.

Data retrieved from NASA's ASRS site as of January 2009 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.

An A320 crew reports that because no NDB receiver is installed in this aircraft type; they could not comply with an engine out procedure at rno requiring navigation to an NDB.