A B737 was issued a pre departure clearance clearance that included an RNAV departure. This aircraft was unable to fly the RNAV; but departed and discovered the error airborne.

Home

Browse by month

Random

Latest

About

Contact

Attributes
ACN	792299
Time
Date	200806
Local Time Of Day	1201 To 1800
Place
Locale Reference	airport : mia.airport
State Reference	FL
Altitude	msl single value : 3000
Environment
Flight Conditions	VMC IMC
Light	Daylight
Aircraft 1
Controlling Facilities	tracon : mia.tracon
Operator	common carrier : air carrier
Make Model Name	B737 Undifferentiated or Other Model
Operating Under FAR Part	Part 121
Navigation In Use	other
Flight Phase	climbout : intermediate altitude
Route In Use	departure sid : n/s
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : atp
Experience	flight time last 90 days : 240 flight time total : 18000 flight time type : 15000
ASRS Report	792299
Events
Anomaly	non adherence : clearance non adherence : company policies non adherence : far non adherence : published procedure other spatial deviation
Independent Detector	other controllera
Resolutory Action	controller : issued new clearance
Supplementary
Problem Areas	Aircraft Flight Crew Human Performance
Primary Problem	Flight Crew Human Performance

Narrative:

We received our clearance via pre departure clearance. We had been warned by our company to be careful and make sure we have the correct departure SID since RNAV sids are becoming popular. Our aircraft is not yet approved for RNAV departures. In the past I have caught on the pre departure clearance an RNAV clearance and then had the clearance delivery correct it. This day I did not catch the RNAV departure. I have been flying out of mia for yrs on the basic departure and it is always the same. This day they slipped in the RNAV departure. I should have caught it. It was not until the departure controller told us to go direct to a fix we did not have in our FMC that the error was observed. It did not present a big problem this day; but we were in the wrong. To correct this problem in the future; I would recommend that if it is going to be an RNAV SID or STAR; there should be the word 'RNAV' preceding the name of the procedure. This would have alerted us. This has happened to other crews both on sids and stars.

Original NASA ASRS Text

Title: A B737 WAS ISSUED A PDC CLRNC THAT INCLUDED AN RNAV DEP. THIS ACFT WAS UNABLE TO FLY THE RNAV; BUT DEPARTED AND DISCOVERED THE ERROR AIRBORNE.

Narrative: WE RECEIVED OUR CLRNC VIA PDC. WE HAD BEEN WARNED BY OUR COMPANY TO BE CAREFUL AND MAKE SURE WE HAVE THE CORRECT DEP SID SINCE RNAV SIDS ARE BECOMING POPULAR. OUR ACFT IS NOT YET APPROVED FOR RNAV DEPS. IN THE PAST I HAVE CAUGHT ON THE PDC AN RNAV CLRNC AND THEN HAD THE CLRNC DELIVERY CORRECT IT. THIS DAY I DID NOT CATCH THE RNAV DEP. I HAVE BEEN FLYING OUT OF MIA FOR YRS ON THE BASIC DEP AND IT IS ALWAYS THE SAME. THIS DAY THEY SLIPPED IN THE RNAV DEP. I SHOULD HAVE CAUGHT IT. IT WAS NOT UNTIL THE DEP CTLR TOLD US TO GO DIRECT TO A FIX WE DID NOT HAVE IN OUR FMC THAT THE ERROR WAS OBSERVED. IT DID NOT PRESENT A BIG PROB THIS DAY; BUT WE WERE IN THE WRONG. TO CORRECT THIS PROB IN THE FUTURE; I WOULD RECOMMEND THAT IF IT IS GOING TO BE AN RNAV SID OR STAR; THERE SHOULD BE THE WORD 'RNAV' PRECEDING THE NAME OF THE PROC. THIS WOULD HAVE ALERTED US. THIS HAS HAPPENED TO OTHER CREWS BOTH ON SIDS AND STARS.

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