A320
Air Traffic Control Fully Certified
Confusion; Situational Awareness
ATC Issue All Types; Deviation / Discrepancy - Procedural Published Material / Policy
General None Reported / Taken
Chart Or Publication; Human Factors; Procedure
Air Carrier X was departing Runway 8 with the route ABQ2...FTI. Assuming that the air carrier would be on the GRIZZ1 RNAV departure; I cleared Air Carrier X for take off without giving a vector. Air Carrier X departed runway heading; towards rapidly increasing MVAs. I think the 'RNAV to (point)' phraseology with the take off clearance would be a good idea for all airports; not just ones with parallel runways. I would suspect that a pilot would question a clearance like 'RNAV to TYILR' if they're expecting a RADAR vector; providing a last minute sanity check. The first fix that shows in the aircraft's tag is different depending on whether the aircraft is on a RNAV or non-RNAV departure. Double checking the field before switching the aircraft to departure would be another last-second chance to fix the problem. Changing local procedures to highlight non-RNAV air carrier or air taxi departures might also help; but it's not necessarily Ground Control's or Clearance Delivery's responsibility check every strip for Local Control.
ABQ Controller described a confused departure route event when unsure if the departing aircraft was issued a RNAV or conventional SID. The reporter suggested a number of procedural changes to reduce future occurrences.