37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 295443 |
Time | |
Date | 199501 |
Day | Tue |
Local Time Of Day | 0601 To 1200 |
Place | |
Locale Reference | airport : bog |
State Reference | FO |
Altitude | agl bound lower : 400 agl bound upper : 1000 |
Environment | |
Flight Conditions | IMC |
Light | Dawn |
Aircraft 1 | |
Controlling Facilities | tracon : bog |
Operator | common carrier : air carrier |
Make Model Name | Commercial Fixed Wing |
Operating Under FAR Part | Part 121 |
Flight Phase | climbout : initial |
Route In Use | departure other departure sid : sid |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
Qualification | pilot : instrument pilot : atp |
Experience | flight time last 90 days : 267 flight time total : 12600 flight time type : 8500 |
ASRS Report | 295443 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : first officer |
Qualification | pilot : instrument pilot : commercial |
Events | |
Anomaly | non adherence : published procedure non adherence : clearance non adherence : far other anomaly other other spatial deviation |
Independent Detector | other controllera other flight crewa |
Resolutory Action | controller : issued new clearance other |
Consequence | faa : reviewed incident with flight crew |
Supplementary | |
Primary Problem | Flight Crew Human Performance |
Air Traffic Incident | Pilot Deviation |
Narrative:
ATC english was extremely poor, but it appeared that we were cleared off runway 13 for an 'IP2' SID. Our company only provided 1 set of communication plates which were kept on the first officer's side. I asked him to find the 'IP2 SID' chart but he said that there wasn't one, so I asked him to pass me all the bogota charts so that I could check for myself. I did not find the chart there. We did find a 'IP1 SID' chart, however, so as our charts had not been amended by our company I assumed that the 'IP2' must be a modification of the IP1 departure. We attempted to clarify this with ATC, but they did not understand. We took off on runway 12 and turned right after takeoff in accordance with the ign 1 SID. At 1000 ft the controller asked us why we had turned right when the ign 2 SID called for a left turn, although we had no knowledge of this. There was no conflict or further comment from the controller, however, we had obviously flown the wrong SID. Much later in the flight, the first officer 'found' the chart for the 'ign 2' SID in his briefcase. His overall performance was so bad that his employment has since been terminated. This was my first visit to bogota, and I believe that the incident would not have happened if 2 sets of charts had been provided by the company. Flight fatigue was also a factor as we had been on duty 16 hours prior to the event, this after a minimum 12 hours rest, preceded by 14 hour duty period.
Original NASA ASRS Text
Title: NAV ERROR -- WRONG SID.
Narrative: ATC ENGLISH WAS EXTREMELY POOR, BUT IT APPEARED THAT WE WERE CLRED OFF RWY 13 FOR AN 'IP2' SID. OUR COMPANY ONLY PROVIDED 1 SET OF COM PLATES WHICH WERE KEPT ON THE FO'S SIDE. I ASKED HIM TO FIND THE 'IP2 SID' CHART BUT HE SAID THAT THERE WASN'T ONE, SO I ASKED HIM TO PASS ME ALL THE BOGOTA CHARTS SO THAT I COULD CHK FOR MYSELF. I DID NOT FIND THE CHART THERE. WE DID FIND A 'IP1 SID' CHART, HOWEVER, SO AS OUR CHARTS HAD NOT BEEN AMENDED BY OUR COMPANY I ASSUMED THAT THE 'IP2' MUST BE A MODIFICATION OF THE IP1 DEP. WE ATTEMPTED TO CLARIFY THIS WITH ATC, BUT THEY DID NOT UNDERSTAND. WE TOOK OFF ON RWY 12 AND TURNED R AFTER TKOF IN ACCORDANCE WITH THE IGN 1 SID. AT 1000 FT THE CTLR ASKED US WHY WE HAD TURNED R WHEN THE IGN 2 SID CALLED FOR A L TURN, ALTHOUGH WE HAD NO KNOWLEDGE OF THIS. THERE WAS NO CONFLICT OR FURTHER COMMENT FROM THE CTLR, HOWEVER, WE HAD OBVIOUSLY FLOWN THE WRONG SID. MUCH LATER IN THE FLT, THE FO 'FOUND' THE CHART FOR THE 'IGN 2' SID IN HIS BRIEFCASE. HIS OVERALL PERFORMANCE WAS SO BAD THAT HIS EMPLOYMENT HAS SINCE BEEN TERMINATED. THIS WAS MY FIRST VISIT TO BOGOTA, AND I BELIEVE THAT THE INCIDENT WOULD NOT HAVE HAPPENED IF 2 SETS OF CHARTS HAD BEEN PROVIDED BY THE COMPANY. FLT FATIGUE WAS ALSO A FACTOR AS WE HAD BEEN ON DUTY 16 HRS PRIOR TO THE EVENT, THIS AFTER A MINIMUM 12 HRS REST, PRECEDED BY 14 HR DUTY PERIOD.
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.