Narrative:

I was distracted by a couple things. 1) I was paying extra attention to the runway intersection at 20-16 as that's a hotspot. And 2) we were cleared for takeoff long before the preceding aircraft had cleared the runway; which was also a distraction. The controller definitely didn't issue the takeoff clearance with 'RNAV to kalli'; which is what I would expect if we were supposed to fly an RNAV departure.taking off from richmond we were given the kalli RNAV departure. We briefed the departure from the [chart]; but we left the lateral mode in heading. We were given our takeoff clearance; and I believed at the time that we were told runway heading. After contacting departure they asked if we were flying the kalli. I said no and they cleared us direct to kalli. Reviewing the takeoff clearance in my head; I think the controller might just have said 'cleared for takeoff;' and of course we should then have flown the RNAV departure.first; it's not uncommon for controllers to omit the 'RNAV to-' phraseology; and there should be emphasis added to that for controllers.second; it's very common to be given an RNAV departure; but to be given a heading instead of flying the departure. I think that should be avoided; because pilots should be planning their lateral mode at the gate; and it's impossible to know for sure one way or the other if there isn't consistency with those departures.third; I need to prioritize the reading of the takeoff clearance above other distractions to be sure that I hear the clearance correctly. I'm not sure we did this departure incorrectly; because I'm not sure he didn't give us a heading; but I should be sure.

Related reports:

Google
 

Original NASA ASRS Text

Title: An air carrier flight crew reported a track deviation occurred when they failed to track the KALLI RNAV departure out of RIC; thinking they were cleared runway heading.

Narrative: I was distracted by a couple things. 1) I was paying extra attention to the runway intersection at 20-16 as that's a hotspot. And 2) we were cleared for takeoff long before the preceding aircraft had cleared the runway; which was also a distraction. The controller definitely didn't issue the Takeoff clearance with 'RNAV to KALLI'; which is what I would expect if we were supposed to fly an RNAV departure.Taking off from Richmond we were given the KALLI RNAV departure. We briefed the departure from the [chart]; but we left the lateral mode in HDG. We were given our takeoff clearance; and I believed at the time that we were told runway heading. After contacting departure they asked if we were flying the KALLI. I said no and they cleared us direct to KALLI. Reviewing the takeoff clearance in my head; I think the controller might just have said 'cleared for takeoff;' and of course we should then have flown the RNAV departure.First; it's not uncommon for controllers to omit the 'RNAV to-' phraseology; and there should be emphasis added to that for controllers.Second; it's very common to be given an RNAV departure; but to be given a heading instead of flying the departure. I think that should be avoided; because pilots should be planning their lateral mode at the gate; and it's impossible to know for sure one way or the other if there isn't consistency with those departures.Third; I need to prioritize the reading of the takeoff clearance above other distractions to be sure that I hear the clearance correctly. I'm not sure we did this departure incorrectly; because I'm not sure he didn't give us a heading; but I should be sure.

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