An A320 crew, taxiing for takeoff at dca, taxied past the hold short line.

Attributes
ACN	544366
Time
Date	200204
Day	Thu
Local Time Of Day	1201 To 1800
Place
Locale Reference	airport : dca.airport
State Reference	DC
Altitude	agl single value : 0
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Operator	common carrier : air carrier
Make Model Name	A320
Operating Under FAR Part	Part 121
Flight Phase	ground : taxi
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : commercial pilot : flight engineer pilot : instrument pilot : multi engine
Experience	flight time last 90 days : 70 flight time total : 7500 flight time type : 1500
ASRS Report	544366
Person 2
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Events
Anomaly	incursion : runway non adherence : published procedure non adherence : far non adherence : clearance
Independent Detector	other flight crewa other flight crewb
Resolutory Action	controller : issued new clearance none taken : detected after the fact
Supplementary
Problem Areas	Airport Flight Crew Human Performance
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

Pushed back from dca gate, short taxi to runway 19. I loaded performance data into FMS, after which the captain and I accomplished the before takeoff checklist. As we approached the runway, the ground controller instructed us to contact the tower with the expectation that we would be 'going right out.' in an effort to assist me in my checklist items, the captain left the frequency to advise the flight attendants and passenger of our imminent departure. I switched to the tower frequency with the understanding that the captain knew that we had not yet been cleared onto the runway. The captain completed his PA announcement, returned to the frequency, and continued to taxi past the hold short line for the runway. I immediately told him to 'hold short,' and the captain stopped the aircraft just beyond the runway hold short line. I contacted the tower, who cleared us onto the runway, and subsequently cleared us for takeoff. No conflict occurred, and the tower made no reference to our error. I believe that our desire to get home quickly on the final leg of our trip, our failure to effectively communicate with one another, our deviation from established flow patterns and our 'rush' to depart contributed to this error.

Original NASA ASRS Text

Title: AN A320 CREW, TAXIING FOR TKOF AT DCA, TAXIED PAST THE HOLD SHORT LINE.

Narrative: PUSHED BACK FROM DCA GATE, SHORT TAXI TO RWY 19. I LOADED PERFORMANCE DATA INTO FMS, AFTER WHICH THE CAPT AND I ACCOMPLISHED THE BEFORE TKOF CHKLIST. AS WE APCHED THE RWY, THE GND CTLR INSTRUCTED US TO CONTACT THE TWR WITH THE EXPECTATION THAT WE WOULD BE 'GOING RIGHT OUT.' IN AN EFFORT TO ASSIST ME IN MY CHKLIST ITEMS, THE CAPT LEFT THE FREQ TO ADVISE THE FLT ATTENDANTS AND PAX OF OUR IMMINENT DEP. I SWITCHED TO THE TWR FREQ WITH THE UNDERSTANDING THAT THE CAPT KNEW THAT WE HAD NOT YET BEEN CLRED ONTO THE RWY. THE CAPT COMPLETED HIS PA ANNOUNCEMENT, RETURNED TO THE FREQ, AND CONTINUED TO TAXI PAST THE HOLD SHORT LINE FOR THE RWY. I IMMEDIATELY TOLD HIM TO 'HOLD SHORT,' AND THE CAPT STOPPED THE ACFT JUST BEYOND THE RWY HOLD SHORT LINE. I CONTACTED THE TWR, WHO CLRED US ONTO THE RWY, AND SUBSEQUENTLY CLRED US FOR TKOF. NO CONFLICT OCCURRED, AND THE TWR MADE NO REF TO OUR ERROR. I BELIEVE THAT OUR DESIRE TO GET HOME QUICKLY ON THE FINAL LEG OF OUR TRIP, OUR FAILURE TO EFFECTIVELY COMMUNICATE WITH ONE ANOTHER, OUR DEV FROM ESTABLISHED FLOW PATTERNS AND OUR 'RUSH' TO DEPART CONTRIBUTED TO THIS ERROR.

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