Narrative:

After an 8 hour reduced rest period, we were scheduled to report for duty at XA50 eastern daylight time at lga. We arrived at the aircraft at approximately XB00. The gate and ground crew were anxious to get the flight going, which resulted in the preflight being interrupted several times. We both did write down the correct clearance. We were cleared off runway 13 at lga with a maspeth climb. To save time, I elected to brief the departure even though this would be an first officer takeoff. Unfortunately, I read the procedure for the whitestone climb in error. I must point out that the aircraft database does not have the published climb profiles loaded for the la guardia nine departure. If it had, the incident probably would not have happened. Immediately after takeoff, the first officer, following the briefed procedure, started a left turn at 2.5 DME. The departure controller immediately caught the error and corrected the situation. I believe the following factors contributed to this error. 1) I was only checked out in the MD80 on fri/jun/03, and am not totally comfortable with all aircraft flows. 2) the first officer had not flown for 62 days prior to this trip. 3) we were task saturated, trying to get the late flight out as soon as we could. As a result, I deviated from our normal practice of the PF briefing the departure. 4) we arrived late the night before, had only reduced rest of 8 hours, and switched to an early morning report on the last day of a 3-DAY trip. As a result, we were still waking up as we started our day. 5) our EFIS flight director guidance 'dumped' immediately after takeoff due to the compass momentarily exceeding allowable tolerances. This added further confusion to the situation. I believe we both performed correctly 99% of the time on that morning. Unfortunately, we both missed a critical piece of information. The controller was on top of things and stepped in before a traffic conflict could occur.

Related reports:

Google
 

Original NASA ASRS Text

Title: FLT CREW OF MD80 FLEW WRONG CLB PROC ON LA GUARDIA DEP FROM LGA. PROC IS NOT SELECTABLE FROM ACFT DATABASE.

Narrative: AFTER AN 8 HR REDUCED REST PERIOD, WE WERE SCHEDULED TO RPT FOR DUTY AT XA50 EASTERN DAYLIGHT TIME AT LGA. WE ARRIVED AT THE ACFT AT APPROX XB00. THE GATE AND GND CREW WERE ANXIOUS TO GET THE FLT GOING, WHICH RESULTED IN THE PREFLT BEING INTERRUPTED SEVERAL TIMES. WE BOTH DID WRITE DOWN THE CORRECT CLRNC. WE WERE CLRED OFF RWY 13 AT LGA WITH A MASPETH CLB. TO SAVE TIME, I ELECTED TO BRIEF THE DEP EVEN THOUGH THIS WOULD BE AN FO TKOF. UNFORTUNATELY, I READ THE PROC FOR THE WHITESTONE CLB IN ERROR. I MUST POINT OUT THAT THE ACFT DATABASE DOES NOT HAVE THE PUBLISHED CLB PROFILES LOADED FOR THE LA GUARDIA NINE DEP. IF IT HAD, THE INCIDENT PROBABLY WOULD NOT HAVE HAPPENED. IMMEDIATELY AFTER TKOF, THE FO, FOLLOWING THE BRIEFED PROC, STARTED A L TURN AT 2.5 DME. THE DEP CTLR IMMEDIATELY CAUGHT THE ERROR AND CORRECTED THE SIT. I BELIEVE THE FOLLOWING FACTORS CONTRIBUTED TO THIS ERROR. 1) I WAS ONLY CHKED OUT IN THE MD80 ON FRI/JUN/03, AND AM NOT TOTALLY COMFORTABLE WITH ALL ACFT FLOWS. 2) THE FO HAD NOT FLOWN FOR 62 DAYS PRIOR TO THIS TRIP. 3) WE WERE TASK SATURATED, TRYING TO GET THE LATE FLT OUT AS SOON AS WE COULD. AS A RESULT, I DEVIATED FROM OUR NORMAL PRACTICE OF THE PF BRIEFING THE DEP. 4) WE ARRIVED LATE THE NIGHT BEFORE, HAD ONLY REDUCED REST OF 8 HRS, AND SWITCHED TO AN EARLY MORNING RPT ON THE LAST DAY OF A 3-DAY TRIP. AS A RESULT, WE WERE STILL WAKING UP AS WE STARTED OUR DAY. 5) OUR EFIS FLT DIRECTOR GUIDANCE 'DUMPED' IMMEDIATELY AFTER TKOF DUE TO THE COMPASS MOMENTARILY EXCEEDING ALLOWABLE TOLERANCES. THIS ADDED FURTHER CONFUSION TO THE SIT. I BELIEVE WE BOTH PERFORMED CORRECTLY 99% OF THE TIME ON THAT MORNING. UNFORTUNATELY, WE BOTH MISSED A CRITICAL PIECE OF INFO. THE CTLR WAS ON TOP OF THINGS AND STEPPED IN BEFORE A TFC CONFLICT COULD OCCUR.

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.