37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1036125 |
Time | |
Date | 201209 |
Local Time Of Day | 1801-2400 |
Place | |
Locale Reference | TTPP.Airport |
State Reference | FO |
Environment | |
Flight Conditions | VMC |
Light | Night |
Aircraft 1 | |
Make Model Name | B767-300 and 300 ER |
Operating Under FAR Part | Part 121 |
Flight Phase | Initial Climb |
Route In Use | Direct |
Flight Plan | IFR |
Person 1 | |
Function | Pilot Not Flying Relief Pilot |
Qualification | Flight Crew Instrument Flight Crew Flight Instructor Flight Crew Air Transport Pilot (ATP) Flight Crew Multiengine |
Experience | Flight Crew Last 90 Days 60 Flight Crew Total 8500 Flight Crew Type 500 |
Person 2 | |
Function | Pilot Not Flying Captain |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Experience | Flight Crew Last 90 Days 67 Flight Crew Total 4000 Flight Crew Type 148 |
Events | |
Anomaly | ATC Issue All Types Deviation - Procedural Published Material / Policy Deviation - Track / Heading All Types Inflight Event / Encounter CFTT / CFIT |
Narrative:
During taxi out from ttpp the tower controller gave us a clearance to: after takeoff proceed direct to logan than on filed route; maintain 15;000 ft. The first officer flying and I asked the tower controller to verify logan as the direct to point after takeoff twice and to actually spell the fix name because the controller was very hard to understand.after takeoff the first officer flying asked for LNAV at 400 ft; our normal procedure to RNAV direct to logan. The controller asked us shortly after this if we had a visual on the terrain to our left; at this point the first officer flying started to turn back to runway heading because turning towards logan did not feel right. The first officer flying had the terrain avoidance system turned on his electronic HSI. At this point we continued on runway heading until 4;100 ft; than we turned left direct to logan. Once we turned back towards runway heading; we didn't turn to logan until 4;100 ft because I remembered that 4;100 ft is normally when you turn on course out of ttpp. I believe one element that caused the problem was the fact that the ttpp tower controller was very difficult to understand and he gave us a clearance direct to a logan after takeoff; not a clearance to logan once we reached 4;100 ft. We all initially felt that since it was a clearance given by the tower; it was reasonable to believe this was a safe departure.in the future; all of us in the flight deck; later that day discussed this departure in great and lengthy detail and we all agreed that from now on; when we are departing an airport we are not totally familiar with; we must always look at the back of the airport page to verify that the instructions given to us by an ATC tower controller; make sense and keep us away from terrain; the fact that the ttpp controller was very hard to understand; complicated matters and the clearance. The main lesson to be learned is; that even a highly experienced international airline crew that has literally flown around the world in wide body jet aircraft; cannot and should not rely on a controller unless the crew is 100% sure the clearance can be carried out safely. Once our crew realized the turn to the left right after takeoff was not correct; we took immediate action to correct it and the rest of the flight was uneventful. Don't let experience lull you into complacency.
Original NASA ASRS Text
Title: A B767-300 departing TTPP misunderstood the meaning of their ATC clearance to proceed direct to LOGAN after takeoff and turned toward it fix prior to completing the Obstacle Clearance procedure which requires runway heading to 4;100 FT before proceeding on course. Difficulty understanding the Controller was cited as a contributing factor.
Narrative: During taxi out from TTPP the Tower Controller gave us a clearance to: After takeoff proceed Direct to LOGAN than on filed route; maintain 15;000 FT. The First Officer flying and I asked the Tower Controller to verify LOGAN as the direct to point after takeoff twice and to actually spell the fix name because the Controller was very hard to understand.After takeoff the First Officer flying asked for LNAV at 400 FT; our normal procedure to RNAV direct to LOGAN. The Controller asked us shortly after this if we had a visual on the terrain to our left; at this point the First Officer flying started to turn back to runway heading because turning towards LOGAN did not feel right. The First Officer flying had the Terrain avoidance system turned on his electronic HSI. At this point we continued on runway heading until 4;100 FT; than we turned left direct to LOGAN. Once we turned back towards runway heading; we didn't turn to LOGAN until 4;100 FT because I remembered that 4;100 FT is normally when you turn on course out of TTPP. I believe one element that caused the problem was the fact that the TTPP Tower Controller was very difficult to understand and he gave us a clearance direct to a LOGAN after takeoff; NOT a clearance to LOGAN once we reached 4;100 FT. We all initially felt that since it was a clearance given by the Tower; it was reasonable to believe this was a safe departure.In the future; all of us in the flight deck; later that day discussed this departure in great and lengthy detail and we ALL agreed that from now on; when we are departing an airport we are not totally familiar with; we MUST always look at the back of the airport page to verify that the instructions given to us by an ATC Tower Controller; make sense and keep us away from terrain; the fact that the TTPP Controller was very hard to understand; complicated matters and the clearance. The main lesson to be learned is; that even a highly experienced International Airline crew that has literally flown around the world in wide body jet aircraft; CANNOT and should not rely on a controller unless the crew is 100% sure the clearance can be carried out safely. Once our crew realized the turn to the left right after takeoff was not correct; we took immediate action to correct it and the rest of the flight was uneventful. Don't let experience lull you into complacency.
Data retrieved from NASA's ASRS site as of July 2013 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.