37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 514439 |
Time | |
Date | 200106 |
Day | Thu |
Local Time Of Day | 1801 To 2400 |
Place | |
Locale Reference | airport : cyqx.airport |
State Reference | NF |
Altitude | msl bound lower : 3000 msl bound upper : 5000 |
Environment | |
Flight Conditions | VMC |
Light | Dusk |
Aircraft 1 | |
Controlling Facilities | tracon : cyqx.tracon tracon : phl.tracon |
Operator | general aviation : corporate |
Make Model Name | Challenger CL601 |
Operating Under FAR Part | Part 91 |
Flight Phase | climbout : intermediate altitude |
Route In Use | departure sid : gander 3 |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : corporate |
Function | flight crew : captain oversight : pic |
Person 2 | |
Affiliation | company : corporate |
Function | flight crew : first officer |
Events | |
Anomaly | non adherence : published procedure non adherence : clearance other anomaly other other spatial deviation |
Independent Detector | other controllera |
Resolutory Action | controller : issued alert flight crew : became reoriented flight crew : returned to intended or assigned course |
Consequence | faa : reviewed incident with flight crew |
Supplementary | |
Problem Areas | Flight Crew Human Performance |
Primary Problem | Flight Crew Human Performance |
Air Traffic Incident | Pilot Deviation |
Narrative:
We departed cyqx, canada bound for london england in our challenger 601. Upon contacting departure, the controller asked us what altitude we were climbing to and we responded FL330. The controller replied no, you were issued the gander 3 departure which requires you to maintain 5000 ft. We had not even reached 3000 ft yet, so we simply leveled at 5000 ft. The controller stated to be more careful in the future, and he immediately issued us a climb to FL280, and we went on our way. There was no traffic conflict at any time, in fact there was no traffic on our TCASII at all. The factors that contributed to the above incident are as follows: first, we were passing through gander on a quick turn, just stopping for fuel. In doing so, we rushed ourselves. It is standard procedure to receive our clearance while taxiing out at gander, this is ordinarily not a big deal, however, picking up an oceanic clearance for those of who do not do it everyday is a bit more complicated. We became preoccupied with ensuring we had the correct clearance entered into our FMS's for the oceanic crossing, and we simply overlooked the gander 3 departure which states 'fly runway heading and maintain 5000 ft.' just after breaking ground I realized we had forgotten to brief the departure so I asked the PNF what the departure read and he said 'fly runway heading.' I corrected the heading but he overlooked the maintain 5000 ft. The tower controller had issued us a clearance to line up and wait on the active runway prior to giving us our oceanic clearance. During our taxi back and line up we received the oceanic clearance. Begin on active runway, running your checklists, and copying clrncs is in my opinion not a good situation. In the future, I will hold short, copy the clearance, brief the clearance, and not allow myself to be rushed. Secondly, a more subjective contributor to the incident is, the pilot I was flying with is our chief pilot and he has self proclaimed himself to be a non detail oriented person. He further explained to me that I am too detailed (compared to him). As a result, as a new hire, trying to fit in I compromised and became a bit too complacent. I am frustrated with myself and have made a promise to myself that I will not try to be like someone else just to fit in, chief pilot or no chief pilot. I truly believe aviation is a detailed oriented business, and by being detailed oriented is how I have been able to succeed. In conclusion, we were lucky, as it turned out, we had only strayed about 20 degrees off the runway heading and we were able to correct it ourselves. We did miss setting the correct altitude in the altitude alerter, however, we were lucky we had not yet passed that altitude (5000 ft). I have learned from this experience and will not allow myself to be pressured into being rushed or pressured into overlooking the details. I hope by passing this incident on to others will be able to learn from our mistake and possibly not succumb to the outside influences that distracted us.
Original NASA ASRS Text
Title: CL60 FLC BECAME DISTRACTED PRIOR TO DEP AND DO NOT BRIEF SID PORTION OF CLRNC.
Narrative: WE DEPARTED CYQX, CANADA BOUND FOR LONDON ENGLAND IN OUR CHALLENGER 601. UPON CONTACTING DEP, THE CTLR ASKED US WHAT ALT WE WERE CLBING TO AND WE RESPONDED FL330. THE CTLR REPLIED NO, YOU WERE ISSUED THE GANDER 3 DEP WHICH REQUIRES YOU TO MAINTAIN 5000 FT. WE HAD NOT EVEN REACHED 3000 FT YET, SO WE SIMPLY LEVELED AT 5000 FT. THE CTLR STATED TO BE MORE CAREFUL IN THE FUTURE, AND HE IMMEDIATELY ISSUED US A CLB TO FL280, AND WE WENT ON OUR WAY. THERE WAS NO TFC CONFLICT AT ANY TIME, IN FACT THERE WAS NO TFC ON OUR TCASII AT ALL. THE FACTORS THAT CONTRIBUTED TO THE ABOVE INCIDENT ARE AS FOLLOWS: FIRST, WE WERE PASSING THROUGH GANDER ON A QUICK TURN, JUST STOPPING FOR FUEL. IN DOING SO, WE RUSHED OURSELVES. IT IS STANDARD PROC TO RECEIVE OUR CLRNC WHILE TAXIING OUT AT GANDER, THIS IS ORDINARILY NOT A BIG DEAL, HOWEVER, PICKING UP AN OCEANIC CLRNC FOR THOSE OF WHO DO NOT DO IT EVERYDAY IS A BIT MORE COMPLICATED. WE BECAME PREOCCUPIED WITH ENSURING WE HAD THE CORRECT CLRNC ENTERED INTO OUR FMS'S FOR THE OCEANIC XING, AND WE SIMPLY OVERLOOKED THE GANDER 3 DEP WHICH STATES 'FLY RWY HEADING AND MAINTAIN 5000 FT.' JUST AFTER BREAKING GND I REALIZED WE HAD FORGOTTEN TO BRIEF THE DEP SO I ASKED THE PNF WHAT THE DEP READ AND HE SAID 'FLY RWY HEADING.' I CORRECTED THE HEADING BUT HE OVERLOOKED THE MAINTAIN 5000 FT. THE TWR CTLR HAD ISSUED US A CLRNC TO LINE UP AND WAIT ON THE ACTIVE RWY PRIOR TO GIVING US OUR OCEANIC CLRNC. DURING OUR TAXI BACK AND LINE UP WE RECEIVED THE OCEANIC CLRNC. BEGIN ON ACTIVE RWY, RUNNING YOUR CHKLISTS, AND COPYING CLRNCS IS IN MY OPINION NOT A GOOD SIT. IN THE FUTURE, I WILL HOLD SHORT, COPY THE CLRNC, BRIEF THE CLRNC, AND NOT ALLOW MYSELF TO BE RUSHED. SECONDLY, A MORE SUBJECTIVE CONTRIBUTOR TO THE INCIDENT IS, THE PLT I WAS FLYING WITH IS OUR CHIEF PLT AND HE HAS SELF PROCLAIMED HIMSELF TO BE A NON DETAIL ORIENTED PERSON. HE FURTHER EXPLAINED TO ME THAT I AM TOO DETAILED (COMPARED TO HIM). AS A RESULT, AS A NEW HIRE, TRYING TO FIT IN I COMPROMISED AND BECAME A BIT TOO COMPLACENT. I AM FRUSTRATED WITH MYSELF AND HAVE MADE A PROMISE TO MYSELF THAT I WILL NOT TRY TO BE LIKE SOMEONE ELSE JUST TO FIT IN, CHIEF PLT OR NO CHIEF PLT. I TRULY BELIEVE AVIATION IS A DETAILED ORIENTED BUSINESS, AND BY BEING DETAILED ORIENTED IS HOW I HAVE BEEN ABLE TO SUCCEED. IN CONCLUSION, WE WERE LUCKY, AS IT TURNED OUT, WE HAD ONLY STRAYED ABOUT 20 DEGS OFF THE RWY HEADING AND WE WERE ABLE TO CORRECT IT OURSELVES. WE DID MISS SETTING THE CORRECT ALT IN THE ALT ALERTER, HOWEVER, WE WERE LUCKY WE HAD NOT YET PASSED THAT ALT (5000 FT). I HAVE LEARNED FROM THIS EXPERIENCE AND WILL NOT ALLOW MYSELF TO BE PRESSURED INTO BEING RUSHED OR PRESSURED INTO OVERLOOKING THE DETAILS. I HOPE BY PASSING THIS INCIDENT ON TO OTHERS WILL BE ABLE TO LEARN FROM OUR MISTAKE AND POSSIBLY NOT SUCCUMB TO THE OUTSIDE INFLUENCES THAT DISTRACTED US.
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.