Narrative:

We were filed via the SWANN3 departure; dqo transition. As is commonly the case; bwi was departing on runway 28. I selected runway 28 and the SWANN3 departure; dqo transition in the mcdu but noticed that it was entered into the mcdu flight plan as merely runway 28; a discontinuity; and then dqo and the rest of our filed route. However; the SWANN3 departure for jets requires a left turn to a heading of 150 degrees at the balance 3 DME. The A319 is generally considered to be a turbojet; so that is how the departure should be coded in the navigation database. Instead; the departure is coded for the propellers departure; which is just to fly runway heading. We worked around it by entering the balance/285/3 fix as the first fix after the runway; and then flew the departure in heading mode; using the PDB01 place/bearing/distance pseudo-waypoint as a marker to remind us to make the turn. We also entered balance as in the rad navigation page; and monitored the DME on the nd to identify exactly when to turn. The reason I'm making this report is because if a pilot trusts the navigation database to be correctly coded (as it usually is) and fails to review the paper or efb version of the departure; he or she will be unaware of the incorrect coding; and is likely to continue straight ahead past the three DME point; potentially infringing on the restricted airspace off the departure end of the runway (as often happens to those flying the terpz departure; hafnr transition; who fail to select the transition correctly). This is 'a violation waiting to happen'. I presume an error was made in the coding of the navigation database; where the engineer doing the coding incorrectly entered the propeller departure instructions rather than the jet instructions.

Google
 

Original NASA ASRS Text

Title: An A319 First Officer discovered that the SWANN3 departure from Runway 28 at BWI does not include the turn to 150 degrees at three DME when inserted into the MCDU.

Narrative: We were filed via the SWANN3 departure; DQO transition. As is commonly the case; BWI was departing on Runway 28. I selected Runway 28 and the SWANN3 departure; DQO transition in the MCDU but noticed that it was entered into the MCDU flight plan as merely Runway 28; a discontinuity; and then DQO and the rest of our filed route. However; the SWANN3 departure for JETS requires a left turn to a heading of 150 degrees at the BAL 3 DME. The A319 is generally considered to be a turbojet; so that is how the departure should be coded in the navigation database. Instead; the departure is coded for the PROPS departure; which is just to fly runway heading. We worked around it by entering the BAL/285/3 fix as the first fix after the runway; and then flew the departure in HDG mode; using the PDB01 place/bearing/distance pseudo-waypoint as a marker to remind us to make the turn. We also entered BAL as in the RAD NAV page; and monitored the DME on the ND to identify exactly when to turn. The reason I'm making this report is because if a pilot trusts the navigation database to be correctly coded (as it usually is) and fails to review the paper or EFB version of the departure; he or she will be unaware of the incorrect coding; and is likely to continue straight ahead past the three DME point; potentially infringing on the restricted airspace off the departure end of the runway (as often happens to those flying the TERPZ departure; HAFNR transition; who fail to select the transition correctly). This is 'a violation waiting to happen'. I presume an error was made in the coding of the navigation database; where the engineer doing the coding incorrectly entered the PROP departure instructions rather than the JET instructions.

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