 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Air carrier takes off from austin using the wrong pre departure clearance. Departure controller was not happy.
| Attributes | |
| ACN | 458589 |
| Time | |
| Date | 199912 |
| Day | Fri |
| Local Time Of Day | 0601 To 1200 |
| Place | |
| Locale Reference | airport : aus.airport |
| State Reference | TX |
| Altitude | msl single value : 4000 |
| Environment | |
| Light | Daylight |
| Aircraft 1 | |
| Controlling Facilities | tracon : aus.tracon |
| Operator | common carrier : air carrier |
| Make Model Name | Fokker 100 |
| Operating Under FAR Part | Part 121 |
| Flight Phase | climbout : initial climbout : takeoff |
| Flight Plan | IFR |
| Person 1 | |
| Affiliation | company : air carrier |
| Function | flight crew : captain oversight : pic |
| Qualification | pilot : atp |
| ASRS Report | 458589 |
| Person 2 | |
| Affiliation | company : air carrier government : faa |
| Function | controller : departure flight crew : first officer |
| Qualification | controller : radar pilot : multi engine pilot : instrument pilot : commercial |
| ASRS Report | 458590 |
| Events | |
| Anomaly | altitude deviation : excursion from assigned altitude non adherence : clearance |
| Independent Detector | other controllera other flight crewa |
| Resolutory Action | controller : issued new clearance |
| Supplementary | |
| Problem Areas | Flight Crew Human Performance |
| Primary Problem | Flight Crew Human Performance |
| Air Traffic Incident | Pilot Deviation |
Narrative:
On departure, tower advised to change squawk code. Then contacted departure. Could not contact them. Went back to tower to verify frequency, stating no one on 124.67. He said to contact on 118.8. Contacting departure control, he asked if tower gave us higher than 4000 ft. Responded no, now looking closely to the pre departure clearance. We then realized that the pre departure clearance that was pulled up was for the previous flight. We had a quick turn of 16 mins. The aircraft was late coming in and we (as we shouldn't have) rushed through the checklist. From that point, we really didn't have a reason to look closer to the pre departure clearance after engine start. That's where all the problems came into play. I can't tell you the number of times I do check the pre departure clearance, closeout, etc, for those errors to surface. Departure controller said there was no conflict. Not to avoid blame, I found that in a short turn situation, the ACARS was not uploaded with our flight, and when requesting the pre departure clearance, it was for the previous flight.
Original NASA ASRS Text
Title: ACR TAKES OFF FROM AUSTIN USING THE WRONG PDC. DEP CTLR WAS NOT HAPPY.
Narrative: ON DEP, TWR ADVISED TO CHANGE SQUAWK CODE. THEN CONTACTED DEP. COULD NOT CONTACT THEM. WENT BACK TO TWR TO VERIFY FREQ, STATING NO ONE ON 124.67. HE SAID TO CONTACT ON 118.8. CONTACTING DEP CTL, HE ASKED IF TWR GAVE US HIGHER THAN 4000 FT. RESPONDED NO, NOW LOOKING CLOSELY TO THE PDC. WE THEN REALIZED THAT THE PDC THAT WAS PULLED UP WAS FOR THE PREVIOUS FLT. WE HAD A QUICK TURN OF 16 MINS. THE ACFT WAS LATE COMING IN AND WE (AS WE SHOULDN'T HAVE) RUSHED THROUGH THE CHKLIST. FROM THAT POINT, WE REALLY DIDN'T HAVE A REASON TO LOOK CLOSER TO THE PDC AFTER ENG START. THAT'S WHERE ALL THE PROBS CAME INTO PLAY. I CAN'T TELL YOU THE NUMBER OF TIMES I DO CHK THE PDC, CLOSEOUT, ETC, FOR THOSE ERRORS TO SURFACE. DEP CTLR SAID THERE WAS NO CONFLICT. NOT TO AVOID BLAME, I FOUND THAT IN A SHORT TURN SIT, THE ACARS WAS NOT UPLOADED WITH OUR FLT, AND WHEN REQUESTING THE PDC, IT WAS FOR THE PREVIOUS FLT.
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.