Narrative:

Both pilots read and discussed the pre-departure clearance (pre departure clearance). The initial clearance stated cleared as filed. Filed flight plan: pbi tbird lbv… in the remarks section was: LMORE1; lmore; departure 125.2; ground 121.9. Neither departure route included a transition route to lbv. This ambiguity led both pilots to believe the departure route was the TBIRD1 tbird lbv which was loaded in the FMS and flown as depicted. On departure because of radio congestion; we were unable to confirm the routing and climb clearance limit and overshot the chart depicted 4000 ft MSL restriction by 300 ft before correcting immediately back to 4000 ft and establishing contact with departure control. Departure control seemed unconcerned about our routing; direct to tbird intersection; gave us direct routing to another fix and a higher altitude. There was no traffic conflict or TCAS TA/RA. Factors contributing to this situation included failure to confirm routing/altitude with clearance before taxi; a short taxi route with inadequate cockpit briefing and inability to contact departure control due to radio congestion. Further; the format of the pre departure clearance; with the amended routing noted in the remarks section; along with frequencies; instead of the route clearance (cleared as filed) section which appears at the top. Last; the efb's (electronic flight bags) make it difficult to see the whole departure plate without scrolling up/down or side to side in a high workload environment. In the future; the crew will resolve any ambiguities in routing/altitude before leaving the chocks and either complete the takeoff briefing before reaching the runway; or request a short delay before accepting takeoff clearance.

Google
 

Original NASA ASRS Text

Title: A Corporate Flight Crew misread a PBI PDC clearance and departed on TBIRD1 RNAV instead of the LNORE1. They failed to resolve ambiguities prior to departure.

Narrative: Both pilots read and discussed the Pre-Departure Clearance (PDC). The initial clearance stated Cleared As Filed. Filed Flight Plan: PBI TBIRD LBV… In the remarks section was: LMORE1; LMORE; DEP 125.2; GND 121.9. Neither departure route included a transition route to LBV. This ambiguity led both pilots to believe the departure route was the TBIRD1 TBIRD LBV which was loaded in the FMS and flown as depicted. On departure because of radio congestion; we were unable to confirm the routing and climb clearance limit and overshot the chart depicted 4000 FT MSL restriction by 300 FT before correcting immediately back to 4000 FT and establishing contact with Departure Control. Departure Control seemed unconcerned about our routing; direct to TBIRD intersection; gave us direct routing to another fix and a higher altitude. There was no traffic conflict or TCAS TA/RA. Factors contributing to this situation included failure to confirm routing/altitude with clearance before taxi; a short taxi route with inadequate cockpit briefing and inability to contact Departure Control due to radio congestion. Further; the format of the PDC; with the amended routing noted in the REMARKS section; along with frequencies; instead of the route clearance (Cleared as Filed) section which appears at the top. Last; the EFB's (Electronic Flight Bags) make it difficult to see the whole departure plate without scrolling up/down or side to side in a high workload environment. In the future; the crew will resolve any ambiguities in routing/altitude before leaving the chocks and either complete the takeoff briefing before reaching the runway; or request a short delay before accepting takeoff clearance.

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.