Narrative:

This was my third trip out of rsw in the last month. It was my second to depart off runway 06. The CSHEL4 RNAV departure is primarily designed to fly off runway 24. When assigned off runway 06 it is radar vectors to cshel to join the departure. When loading the GPS/FMS selecting the CSHEL4 and runway 06...cshel does not appear on the legs page and must be entered manually...(you will only realize this if you have done it before since cshel is not on the flight plan when checking points as we are never filed for the cshel departure when using runway 06). Today we were filed: J75 tay J85 amg etc. Our clearance; which was 'revised' read: CSHEL4 lal transition corsu tay flight plan route. We had clearance delivery read it twice to make sure we heard it correctly. I interpreted the clearance to mean that once on the lal transition; we were cleared direct corsu and loaded the GPS accordingly...since the verbiage was not after lal direct corsu. After airborne and cleared direct cshel; the first officer asked if we should follow the lal transition and then go direct cshel. I then queried departure for clarification asking 'after cshel; are we cleared direct corsu'? The answer was 'affirmative' so we proceeded accordingly. Shortly after switching to mia center we were asked if we were going to lal...I advised we were thought to be cleared direct corsu. We were then told go lal then corsu...and we complied. Suggestions; I believe communications between ATC and pilots has deteriorated over the last few years. As the new controllers have arrived it's almost like we speak different languages. Often times I feel we have to interpret things that should be clear. I have no problem asking for clarification. Obviously; this time...asking twice; I still got it wrong...and I accept responsibility. We must strive to be absolutely correct so we and ATC are on the same page.

Related reports:

Google
 

Original NASA ASRS Text

Title: RSW Air Carrier departure described confused SID/Route assignment listing less than clear communications with ATC as a causal factor.

Narrative: This was my third trip out of RSW in the last month. It was my second to depart off Runway 06. The CSHEL4 RNAV Departure is primarily designed to fly off Runway 24. When assigned off Runway 06 it is RADAR vectors to CSHEL to join the departure. When loading the GPS/FMS selecting the CSHEL4 and Runway 06...CSHEL does not appear on the legs page and must be entered manually...(you will only realize this if you have done it before since CSHEL is NOT on the flight plan when checking points as we are NEVER filed for the CSHEL departure when using Runway 06). Today we were filed: J75 TAY J85 AMG etc. Our Clearance; which was 'revised' read: CSHEL4 LAL Transition CORSU TAY flight plan route. We had Clearance Delivery read it twice to make sure we heard it correctly. I interpreted the clearance to mean that once on the LAL transition; we were cleared direct CORSU and loaded the GPS accordingly...since the verbiage was not after LAL direct CORSU. After airborne and cleared direct CSHEL; the First Officer asked if we should follow the LAL transition and then go direct CSHEL. I then queried departure for clarification asking 'after CSHEL; are we cleared direct CORSU'? The answer was 'affirmative' so we proceeded accordingly. Shortly after switching to MIA Center we were asked if we were going to LAL...I advised we were thought to be cleared direct CORSU. We were then told go LAL then CORSU...and we complied. Suggestions; I believe communications between ATC and pilots has deteriorated over the last few years. As the new controllers have arrived it's almost like we speak different languages. Often times I feel we have to interpret things that should be clear. I have no problem asking for clarification. Obviously; this time...asking twice; I still got it wrong...and I accept responsibility. We must strive to be ABSOLUTELY correct so we and ATC are on the same page.

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