37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1333069 |
Time | |
Date | 201502 |
Local Time Of Day | 0601-1200 |
Place | |
Locale Reference | PDX.Airport |
State Reference | OR |
Environment | |
Flight Conditions | Marginal |
Light | Daylight |
Aircraft 1 | |
Make Model Name | Light Transport Low Wing 2 Turbojet Eng |
Operating Under FAR Part | Part 91 |
Flight Phase | Taxi |
Route In Use | Vectors SID MINNE 5 |
Flight Plan | IFR |
Person 1 | |
Function | Captain Pilot Flying |
Qualification | Flight Crew Air Transport Pilot (ATP) Flight Crew Flight Instructor Flight Crew Multiengine Flight Crew Instrument |
Experience | Flight Crew Last 90 Days 40 Flight Crew Total 4700 Flight Crew Type 175 |
Events | |
Anomaly | ATC Issue All Types Deviation - Procedural Published Material / Policy |
Narrative:
I filed the minne 5 departure hisku transition. When I received the clearance from pdx clearance delivery frequency; I was assigned the portland 1 departure; then as filed. This is somewhat common at pdx so I didn't question the issuance of a different SID than filed. Everything was normal until we were cleared for takeoff on runway 28R. The tower told us to fly the minne 5 departure and cleared us for takeoff and to not delay since there was an aircraft of short final. My first officer stated that we were issued the portland 1 departure and requested a radar vector on the departure; otherwise we would have to reset everything in the flight management system; re-brief the departure; and run additional checklists. The tower controller agreed and we began the takeoff roll with a clearance to fly runway heading. Very shortly after departure (about 500 feet AGL) we were recleared as follows: 'cleared direct pegty and the remainder of the minne 5 departure. Climb and maintain 7000.' we were able to safely manage the FMS and get everything reset; but we were busy and somewhat distracted. At no point did I feel safety was compromised; but the workload increased significantly. In the future I would like to taxi clear of the runway and get things sorted out before taking flight. I feel the controller was caught off guard and then felt pressure to get us airborne due to the landing aircraft. This was the first flight of the day for our crew and we both had more than 24 hours rest. Fatigue was not a factor. We utilized good crew resource management to handle the event and had a thorough debrief afterward. The event will be documented within our company safety management system for analysis.
Original NASA ASRS Text
Title: Corporate flight crew reported an increased workload on departure when they received a different SID clearance from Tower than what was received from Clearance Delivery.
Narrative: I filed the MINNE 5 Departure HISKU Transition. When I received the clearance from PDX clearance delivery frequency; I was assigned the Portland 1 Departure; then as filed. This is somewhat common at PDX so I didn't question the issuance of a different SID than filed. Everything was normal until we were cleared for takeoff on Runway 28R. The Tower told us to fly the MINNE 5 Departure and cleared us for takeoff and to not delay since there was an aircraft of short final. My first officer stated that we were issued the Portland 1 Departure and requested a radar vector on the departure; otherwise we would have to reset everything in the flight management system; re-brief the departure; and run additional checklists. The Tower Controller agreed and we began the takeoff roll with a clearance to fly runway heading. Very shortly after departure (about 500 feet AGL) we were recleared as follows: 'cleared direct PEGTY and the remainder of the MINNE 5 Departure. Climb and maintain 7000.' We were able to safely manage the FMS and get everything reset; but we were busy and somewhat distracted. At no point did I feel safety was compromised; but the workload increased significantly. In the future I would like to taxi clear of the runway and get things sorted out before taking flight. I feel the controller was caught off guard and then felt pressure to get us airborne due to the landing aircraft. This was the first flight of the day for our crew and we both had more than 24 hours rest. Fatigue was not a factor. We utilized good crew resource management to handle the event and had a thorough debrief afterward. The event will be documented within our company safety management system for analysis.
Data retrieved from NASA's ASRS site 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.