 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
The pre departure clearance did not match filed route. Crew flew the riled route until questioned by ATC.
| Attributes | |
| ACN | 470820 |
| Time | |
| Date | 200004 |
| Day | Thu |
| Local Time Of Day | 0601 To 1200 |
| Place | |
| Locale Reference | navaid : ffu.vortac |
| State Reference | UT |
| Altitude | msl single value : 28000 |
| Environment | |
| Flight Conditions | VMC |
| Light | Daylight |
| Aircraft 1 | |
| Controlling Facilities | tracon : s56.tracon |
| Make Model Name | B757 Undifferentiated or Other Model |
| Operating Under FAR Part | Part 121 |
| Navigation In Use | other |
| Flight Phase | climbout : vacating altitude |
| Route In Use | departure sid : ffu.4 |
| Flight Plan | IFR |
| Person 1 | |
| Affiliation | company : air carrier |
| Function | flight crew : captain oversight : pic |
| Qualification | pilot : atp |
| Experience | flight time last 90 days : 180 flight time total : 13000 flight time type : 480 |
| ASRS Report | 470280 |
| Person 2 | |
| Affiliation | company : air carrier |
| Function | flight crew : first officer |
| Qualification | pilot : commercial pilot : instrument pilot : multi engine |
| Events | |
| Anomaly | non adherence : company policies non adherence : clearance non adherence : published procedure other spatial deviation |
| Independent Detector | other controllerb |
| Resolutory Action | controller : issued new clearance flight crew : became reoriented |
| Supplementary | |
| Problem Areas | Flight Crew Human Performance |
| Primary Problem | Flight Crew Human Performance |
| Air Traffic Incident | Pilot Deviation |
Narrative:
Our original flight plan was filed slc-mlf...fpr (as filed). Our pre departure clearance stated ffu 4 departure. Upon reaching ffu on departure, instead of proceeding out the ffu 170 degree radial, we proceeded direct mlf. Controller asked us if we were filed direct mlf, and I initially responded 'yes.' I then checked out pre departure clearance and realized we needed to be on the ffu 4 departure. I informed our controller of our mistake and he told us to proceed direct mlf. In retrospect, I realize I (as the PNF, and as the captain) should have confirmed our routing and ensured compliance. I did overlook the fact that the ffu 4 was on our pre departure clearance and did not concur with our flight plan as it was loaded in our FMS. I would, however, recommend that we make every attempt to file our flight plans as we anticipate the departure to be. We regularly depart slc having loaded the flight plan as we did, only to have the pre departure clearance change our routing.
Original NASA ASRS Text
Title: THE PDC DID NOT MATCH FILED RTE. CREW FLEW THE RILED RTE UNTIL QUESTIONED BY ATC.
Narrative: OUR ORIGINAL FLT PLAN WAS FILED SLC-MLF...FPR (AS FILED). OUR PDC STATED FFU 4 DEP. UPON REACHING FFU ON DEP, INSTEAD OF PROCEEDING OUT THE FFU 170 DEG RADIAL, WE PROCEEDED DIRECT MLF. CTLR ASKED US IF WE WERE FILED DIRECT MLF, AND I INITIALLY RESPONDED 'YES.' I THEN CHKED OUT PDC AND REALIZED WE NEEDED TO BE ON THE FFU 4 DEP. I INFORMED OUR CTLR OF OUR MISTAKE AND HE TOLD US TO PROCEED DIRECT MLF. IN RETROSPECT, I REALIZE I (AS THE PNF, AND AS THE CAPT) SHOULD HAVE CONFIRMED OUR ROUTING AND ENSURED COMPLIANCE. I DID OVERLOOK THE FACT THAT THE FFU 4 WAS ON OUR PDC AND DID NOT CONCUR WITH OUR FLT PLAN AS IT WAS LOADED IN OUR FMS. I WOULD, HOWEVER, RECOMMEND THAT WE MAKE EVERY ATTEMPT TO FILE OUR FLT PLANS AS WE ANTICIPATE THE DEP TO BE. WE REGULARLY DEPART SLC HAVING LOADED THE FLT PLAN AS WE DID, ONLY TO HAVE THE PDC CHANGE OUR ROUTING.
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.