 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
B737 flight crew assumes las tower clearance to 'expect vectors' on departure from aaces RNAV SID supersede SID navigation requirements prior to aaces intersection instead of 'expect vectors' after aaces intersection as published.
| Attributes | |
| ACN | 561949 |
| Time | |
| Date | 200210 |
| Day | Sat |
| Local Time Of Day | 1201 To 1800 |
| Place | |
| Locale Reference | airport : las.airport |
| State Reference | NV |
| Altitude | msl single value : 5000 |
| Environment | |
| Flight Conditions | VMC |
| Light | Daylight |
| Aircraft 1 | |
| Controlling Facilities | tracon : l30.tracon |
| Operator | common carrier : air carrier |
| Make Model Name | B737-300 |
| Operating Under FAR Part | Part 121 |
| Navigation In Use | other |
| Flight Phase | climbout : initial |
| Route In Use | departure sid : aaces rnav one |
| Flight Plan | IFR |
| Person 1 | |
| Affiliation | company : air carrier |
| Function | flight crew : captain oversight : pic |
| Qualification | pilot : atp |
| Experience | flight time last 90 days : 130 flight time total : 9140 flight time type : 2350 |
| ASRS Report | 561949 |
| Person 2 | |
| Affiliation | company : air carrier |
| Function | flight crew : first officer |
| Events | |
| Anomaly | non adherence : published procedure non adherence : clearance other spatial deviation |
| Independent Detector | atc equipment other atc equipment : radar other controllera |
| Resolutory Action | controller : issued new clearance controller : issued advisory |
| Consequence | faa : reviewed incident with flight crew |
| Supplementary | |
| Problem Areas | Flight Crew Human Performance ATC Human Performance Chart Or Publication |
| Primary Problem | Flight Crew Human Performance |
| Air Traffic Incident | Pilot Deviation |
| Situations | |
| Chart | sid : aaces rnav |
Narrative:
Las clearance delivery gave instructions to expect vectors to the aaces departure. Tower cleared us for takeoff without any further instructions. We flew runway heading awaiting vectors from departure control. At approximately 5 NM, departure control asked us if we were assigned runway heading. We told them that we were expecting vectors to the departure. Although departure control didn't say anything else, it sounded like they expected us to fly the RNAV departure. It seems with our recent company letter on las RNAV departures, the clearance we were given, and the expectations of departure control, there is still confusion on proper las departure procedures.
Original NASA ASRS Text
Title: B737 FLC ASSUMES LAS TWR CLRNC TO 'EXPECT VECTORS' ON DEP FROM AACES RNAV SID SUPERSEDE SID NAV REQUIREMENTS PRIOR TO AACES INTXN INSTEAD OF 'EXPECT VECTORS' AFTER AACES INTXN AS PUBLISHED.
Narrative: LAS CLRNC DELIVERY GAVE INSTRUCTIONS TO EXPECT VECTORS TO THE AACES DEP. TWR CLRED US FOR TKOF WITHOUT ANY FURTHER INSTRUCTIONS. WE FLEW RWY HDG AWAITING VECTORS FROM DEP CTL. AT APPROX 5 NM, DEP CTL ASKED US IF WE WERE ASSIGNED RWY HDG. WE TOLD THEM THAT WE WERE EXPECTING VECTORS TO THE DEP. ALTHOUGH DEP CTL DIDN'T SAY ANYTHING ELSE, IT SOUNDED LIKE THEY EXPECTED US TO FLY THE RNAV DEP. IT SEEMS WITH OUR RECENT COMPANY LETTER ON LAS RNAV DEPS, THE CLRNC WE WERE GIVEN, AND THE EXPECTATIONS OF DEP CTL, THERE IS STILL CONFUSION ON PROPER LAS DEP PROCS.
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.