37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 506420 |
Time | |
Date | 200103 |
Day | Thu |
Place | |
Locale Reference | airport : ase.airport |
State Reference | CO |
Altitude | msl bound lower : 7800 msl bound upper : 16000 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Operator | general aviation : corporate |
Make Model Name | Light Transport, Low Wing, 2 Turbojet Eng |
Flight Phase | climbout : intermediate altitude ground : takeoff roll |
Route In Use | departure sid : lindz 4 |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : corporate |
Function | flight crew : first officer |
Qualification | pilot : multi engine pilot : cfi pilot : atp |
Experience | flight time last 90 days : 115 flight time total : 16705 flight time type : 37 |
ASRS Report | 506420 |
Events | |
Anomaly | ground encounters other non adherence : published procedure non adherence : far non adherence : company policies non adherence : clearance other anomaly other |
Resolutory Action | controller : issued new clearance none taken : detected after the fact |
Supplementary | |
Problem Areas | Flight Crew Human Performance |
Primary Problem | Flight Crew Human Performance |
Air Traffic Incident | Pilot Deviation |
Narrative:
We taxied for departure after receiving our IFR clearance. As the sic (PNF) on this leg, I gave the checklist challenges and the captain (PF) gave the appropriate responses. We completed the before takeoff checklist as we approached the runway threshold. Holding short of the runway, the captain asked me to advise the tower we were ready for takeoff. He made a cabin call to tell our passenger to check their seatbelts and I told the tower we were ready for departure. Verifying departure frequency and transponder code from our flight log, I acknowledged the tower's clearance by reading it back. Thinking we had received our takeoff clearance, I told the captain we were ready for takeoff. At this time there was also some disturbance behind us, as one of the passenger was out of his seat and the captain diverted his attention to ask him to be seated as we were ready for takeoff. Lining up on the runway we completed our line-up checks and I told the captain I was ready. The captain advanced the power and I began to monitor the instruments to make the callouts. We were accelerating rapidly when the tower called us '...you are not cleared for takeoff, abort your takeoff!' at this point in the takeoff from this high altitude airport, it appeared unsafe to attempt a high speed abort. The captain visually cleared the runway ahead and the departure path and said we needed to configure, which I believe under the circumstances was the safer action. The tower then said '...cancel your takeoff clearance' at which time we were rotating for liftoff. As we were climbing out, we refocused our attention on flying the airplane and continuing with the after takeoff/climb procedures. The tower asked if we could hear them and I responded I could now hear their calls. They advised us of a previously departed C421 on IFR departure 5 mi to the north and climbing out of 10500 ft. To avoid a traffic conflict, we maintained a 340 degree heading and requested a VFR climb to 16000 ft. The tower cleared us for a VFR climb and told us to call departure control. We avoided the advised traffic with reference to our TCASII and visually looking for the aircraft. There was no TCASII alert or evasive action required. Later we called the tower. They said they had reviewed the tapes and had cleared us 'into position and hold,' which they said I had read back. Next they had advised us that there would be a couple min hold due to departed IFR traffic. I had not responded to (nor do I remember hearing) this transmission. As the tower said the tapes revealed I had read back their clearance, I obviously missed the intent of their clearance, even though I read it back. Contributing factors included a feeling of being rushed to complete the checklist items and verify the frequencys and codes were set in for takeoff, the added confusion of a passenger not being seated and a possible microphone being inadvertently activated when the tower was trying to communication the delay message. This was a very serious error and causes me to again not allow what is happening to make us rush and not carefully verify our clrncs. I believe the captain's continuing the departure was the safe choice when a rejected takeoff under this situation may have led to an overrun. After over 30 yrs of professional flying, I realize that I can still make mistakes and I must continue to exercise care.
Original NASA ASRS Text
Title: BIZJET CREW TOOK OFF WITHOUT CLRNC.
Narrative: WE TAXIED FOR DEP AFTER RECEIVING OUR IFR CLRNC. AS THE SIC (PNF) ON THIS LEG, I GAVE THE CHKLIST CHALLENGES AND THE CAPT (PF) GAVE THE APPROPRIATE RESPONSES. WE COMPLETED THE BEFORE TKOF CHKLIST AS WE APCHED THE RWY THRESHOLD. HOLDING SHORT OF THE RWY, THE CAPT ASKED ME TO ADVISE THE TWR WE WERE READY FOR TKOF. HE MADE A CABIN CALL TO TELL OUR PAX TO CHK THEIR SEATBELTS AND I TOLD THE TWR WE WERE READY FOR DEP. VERIFYING DEP FREQ AND XPONDER CODE FROM OUR FLT LOG, I ACKNOWLEDGED THE TWR'S CLRNC BY READING IT BACK. THINKING WE HAD RECEIVED OUR TKOF CLRNC, I TOLD THE CAPT WE WERE READY FOR TKOF. AT THIS TIME THERE WAS ALSO SOME DISTURBANCE BEHIND US, AS ONE OF THE PAX WAS OUT OF HIS SEAT AND THE CAPT DIVERTED HIS ATTN TO ASK HIM TO BE SEATED AS WE WERE READY FOR TKOF. LINING UP ON THE RWY WE COMPLETED OUR LINE-UP CHKS AND I TOLD THE CAPT I WAS READY. THE CAPT ADVANCED THE PWR AND I BEGAN TO MONITOR THE INSTS TO MAKE THE CALLOUTS. WE WERE ACCELERATING RAPIDLY WHEN THE TWR CALLED US '...YOU ARE NOT CLRED FOR TKOF, ABORT YOUR TKOF!' AT THIS POINT IN THE TKOF FROM THIS HIGH ALT ARPT, IT APPEARED UNSAFE TO ATTEMPT A HIGH SPD ABORT. THE CAPT VISUALLY CLRED THE RWY AHEAD AND THE DEP PATH AND SAID WE NEEDED TO CONFIGURE, WHICH I BELIEVE UNDER THE CIRCUMSTANCES WAS THE SAFER ACTION. THE TWR THEN SAID '...CANCEL YOUR TKOF CLRNC' AT WHICH TIME WE WERE ROTATING FOR LIFTOFF. AS WE WERE CLBING OUT, WE REFOCUSED OUR ATTN ON FLYING THE AIRPLANE AND CONTINUING WITH THE AFTER TKOF/CLB PROCS. THE TWR ASKED IF WE COULD HEAR THEM AND I RESPONDED I COULD NOW HEAR THEIR CALLS. THEY ADVISED US OF A PREVIOUSLY DEPARTED C421 ON IFR DEP 5 MI TO THE N AND CLBING OUT OF 10500 FT. TO AVOID A TFC CONFLICT, WE MAINTAINED A 340 DEG HDG AND REQUESTED A VFR CLB TO 16000 FT. THE TWR CLRED US FOR A VFR CLB AND TOLD US TO CALL DEP CTL. WE AVOIDED THE ADVISED TFC WITH REF TO OUR TCASII AND VISUALLY LOOKING FOR THE ACFT. THERE WAS NO TCASII ALERT OR EVASIVE ACTION REQUIRED. LATER WE CALLED THE TWR. THEY SAID THEY HAD REVIEWED THE TAPES AND HAD CLRED US 'INTO POS AND HOLD,' WHICH THEY SAID I HAD READ BACK. NEXT THEY HAD ADVISED US THAT THERE WOULD BE A COUPLE MIN HOLD DUE TO DEPARTED IFR TFC. I HAD NOT RESPONDED TO (NOR DO I REMEMBER HEARING) THIS XMISSION. AS THE TWR SAID THE TAPES REVEALED I HAD READ BACK THEIR CLRNC, I OBVIOUSLY MISSED THE INTENT OF THEIR CLRNC, EVEN THOUGH I READ IT BACK. CONTRIBUTING FACTORS INCLUDED A FEELING OF BEING RUSHED TO COMPLETE THE CHKLIST ITEMS AND VERIFY THE FREQS AND CODES WERE SET IN FOR TKOF, THE ADDED CONFUSION OF A PAX NOT BEING SEATED AND A POSSIBLE MIKE BEING INADVERTENTLY ACTIVATED WHEN THE TWR WAS TRYING TO COM THE DELAY MESSAGE. THIS WAS A VERY SERIOUS ERROR AND CAUSES ME TO AGAIN NOT ALLOW WHAT IS HAPPENING TO MAKE US RUSH AND NOT CAREFULLY VERIFY OUR CLRNCS. I BELIEVE THE CAPT'S CONTINUING THE DEP WAS THE SAFE CHOICE WHEN A REJECTED TKOF UNDER THIS SIT MAY HAVE LED TO AN OVERRUN. AFTER OVER 30 YRS OF PROFESSIONAL FLYING, I REALIZE THAT I CAN STILL MAKE MISTAKES AND I MUST CONTINUE TO EXERCISE CARE.
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.