2006-06 · NASA ASRS report 699787
A319 FLT CREW HAS A TRACK HDG DEV ON DEP FROM DCA.
AS THE CAPT I HAD A GREAT DEAL OF PAPERWORK DUTIES REGARDING A NUMBER OF MAINT ISSUES: THEREFORE; THE FO HAD ENTERED THE FLT PLAN INTO THE MCDU. ONCE FINISHED WITH THE PAPERWORK; I HURRIEDLY CHKED THE FO'S ENTRIES AND BRIEFED THE DEP AS I WAS THE PF AND WE WERE ALREADY BOARDED WITH PAX AND LATE TO PUSH BACK FROM THE GATE. IN DOING SO; I CHKED THE P-56 AIRSPACE AVOIDANCE PROC AND VERIFIED THAT THE FO HAD CORRECTLY ENTERED A PLACE/BEARING/DISTANCE FOR THE DCA 328 DEG RADIAL WITH THE DCA VOR BEING THE ANCHOR POINT. THE FO HAD A 300 DEG HDG PRE-SELECTED WHICH I EXPLAINED TO HIM 'WASN'T NECESSARY AS THIS IS A FULLY MANAGED DEP.' ON TKOF AT 30 FT THE NAV MODE ENGAGED; HOWEVER; I QUICKLY REALIZED THAT THE FLT DIRECTOR COMMAND BARS WERE NOT COMMANDING A TURN TO THE L WHICH WAS REQUIRED TO AVOID P-56. I; THEREFORE; ROLLED THE ACFT INTO A L TURN AND BRIEFLY CAUGHT A VIEW OF THE PENTAGON FROM THE L WINDOW AND MADE A MENTAL NOTE THAT THE POSITIONING APPEARED TO STILL BE GOOD. I BEGAN DECREASING THE BANK ANGLE IN AN ATTEMPT TO RESYNCHRONIZE WITH THE COMMAND BARS AS I HAD BEEN CONVINCED THAT THE COMMAND BARS SHOULD BE PROVIDING VALID GUIDANCE. AT THIS POINT I NOTED THAT I WAS ALMOST WINGS LEVEL ON A HDG OF APPROX 335-340 DEGS; AND THEN LOOKED TO THE FO'S RAW DATA AND VERIFIED THAT WE WERE STILL CONSIDERABLY R OF COURSE; WHICH WAS N OF THE DCA 328 DEG RADIAL. AT THAT SAME MOMENT THE 'CROSS TRACK ERROR' ILLUMINATED ON MY NAV DISPLAY AND INDICATED WE WERE .4 TO .5 MI OFF COURSE. I IMMEDIATELY TURNED THE ACFT TO THE L AND QUICKLY INTERCEPTED THE DCA 328 DEG RADIAL. AFTER LEVELING AT THE CRUISE ALT I BEGAN DISCUSSING THE DEP WITH THE FO TO DETERMINE WHY THE ACFT DID NOT COMMAND THE REQUIRED L TURN AFTER LIFTOFF. THE FO REMARKED THAT HE 'NEVER HAS LUCK WITH THAT PROC.' AFTER SOME DISCUSSION; I FINALLY REALIZED THAT THE CAUSE OF THE ERROR WAS OUR FAILURE TO DELETE 'THE DEFAULT ACCELERATION ALT PSEUDO WAYPOINT' WHICH IS AUTOMATICALLY PLACED IN THE FLT PLAN IN-LINE WITH THE DEP RWY CTRLINE; WHICH IN TURN COMMANDS THE ACFT TO THAT POINT. THE FO EXPLAINED THAT HE WAS NOT AWARE THAT HE SHOULD HAVE DELETED THIS FROM THE FLT PLAN. EVEN THOUGH HE DID RECALL THE SAME PROC BEING UTILIZED AT A PREVIOUS AIRLINE HE HAD FLOWN FOR. I DO NOT FEEL THAT WE ACTUALLY PENETRATED THE P-56 AIRSPACE. HOWEVER; I DO BELIEVE WE CAME EXTREMELY CLOSE (APPROX .125 MI) TO THE BOUNDARY WHEN WE SHOULD NOT HAVE. ALTHOUGH I DO FEEL THAT THE WORKLOAD AND TIME CONSTRAINTS AT THE GATE CONTRIBUTED TO THIS OVERSIGHT; I TAKE RESPONSIBILITY FOR THIS ERROR AS I FAILED TO REALIZE THAT THE PSEUDO WAYPOINT WAS LEFT WITHIN THE FLT PLAN.
More incidents for this aircraft family
Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.
Loading the flight search…
Pick an aircraft model — Boeing 737, Airbus A320, A380, Boeing 787 Dreamliner and more — enter your origin airport, and FlightFinder shows every route that plane flies from there with live fares.
We support Boeing 737/747/757/767/777/787, the full Airbus A220/A319/A320/A321/A330/A340/A350/A380 family, Embraer E170/E175/E190/E195, Bombardier CRJ and Dash 8, and the ATR 42/72 turboprops.
Search and schedules are free. Pro ($4.99/month, $39/year, or $99 one-time lifetime) unlocks the enriched flight card — on-time stats, CO₂ per passenger, amenities, live gate & weather — plus My Trips with push alerts.
Live schedules come from Amadeus, AeroDataBox and Travelpayouts. Observed routes (which aircraft actually flew a given city pair) are crowdsourced from adsb.lol ADS-B data under the Open Database License.