 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
An SF340 flight crew performs an unauthorized takeoff when dealing with faulty radio receptions at cyqb, pq.
| Attributes | |
| ACN | 518099 |
| Time | |
| Date | 200107 |
| Day | Sun |
| Local Time Of Day | 1201 To 1800 |
| Place | |
| Locale Reference | airport : cyqb.airport |
| State Reference | PQ |
| Altitude | agl single value : 0 |
| Environment | |
| Flight Conditions | VMC |
| Light | Daylight |
| Aircraft 1 | |
| Operator | common carrier : air carrier |
| Make Model Name | SF 340A |
| Operating Under FAR Part | Part 121 |
| Flight Phase | climbout : takeoff ground : position and hold |
| Flight Plan | IFR |
| Person 1 | |
| Affiliation | company : air carrier |
| Function | flight crew : captain oversight : pic |
| Qualification | pilot : cfi pilot : atp |
| Experience | flight time last 90 days : 220 flight time total : 7000 flight time type : 520 |
| ASRS Report | 518099 |
| Person 2 | |
| Affiliation | company : air carrier |
| Function | flight crew : first officer |
| Experience | flight time last 90 days : 200 flight time total : 1300 flight time type : 220 |
| ASRS Report | 518097 |
| Events | |
| Anomaly | aircraft equipment problem : less severe airspace violation : entry non adherence : clearance other anomaly other |
| Independent Detector | other controllera |
| Resolutory Action | none taken : detected after the fact |
| Consequence | faa : reviewed incident with flight crew |
| Supplementary | |
| Problem Areas | ATC Human Performance Aircraft ATC Facility |
| Primary Problem | Flight Crew Human Performance |
| Air Traffic Incident | Pilot Deviation |
Narrative:
We were given 'position and wait' by tower on runway 6. Their radio was very bad -- full of static and broken up. They issued what I was certain of a takeoff clearance, but I could not understand the altitude and vector. My first officer and I both asked them to repeat it several times and advised them that their radio was nearly unreadable. Finally, another voice on another radio stopped in and clarified the altitude and vector. About 1/2 way down the runway I heard another transmission, but it was completely garbled. I stated 'unreadable' in response. Immediately after takeoff, I switched over to departure. She advised me that we did not have a takeoff clearance (the one thing I was sure I had heard). Obviously, the big element here was the abysmally bad tower radio. Secondarily, I should have insisted on a clear transmission of the entire clearance, but -- and this is always a practice that increases pressure to go on a flight crew -- we had been positioned on the active runway for a considerable period of time by then. I know from personal experience that being on tower control is no guarantee that no one will try to land on top of you. Supplemental information from acn 518097: when receiving our taxi clearance from the ground controller, I informed him that his transmission was very broken and hard to understand. After he repeated the clearance, I could understand it enough to repeat it back to him with his satisfaction. We taxied to the hold line for runway. We were given position and wait on runway 6. While in position, the controller amended our clearance with a new heading of 120 degrees and 3000 ft. I asked for verification twice and the captain then asked for verification and was satisfied with his answer. We started the takeoff roll. We should have stayed in position and had them try another transmitter until we could clearly understand the tower controller. The situation did not seem to cause any dangerous situation or a conflict with any other aircraft. But it could have.
Original NASA ASRS Text
Title: AN SF340 FLC PERFORMS AN UNAUTH TKOF WHEN DEALING WITH FAULTY RADIO RECEPTIONS AT CYQB, PQ.
Narrative: WE WERE GIVEN 'POS AND WAIT' BY TWR ON RWY 6. THEIR RADIO WAS VERY BAD -- FULL OF STATIC AND BROKEN UP. THEY ISSUED WHAT I WAS CERTAIN OF A TKOF CLRNC, BUT I COULD NOT UNDERSTAND THE ALT AND VECTOR. MY FO AND I BOTH ASKED THEM TO REPEAT IT SEVERAL TIMES AND ADVISED THEM THAT THEIR RADIO WAS NEARLY UNREADABLE. FINALLY, ANOTHER VOICE ON ANOTHER RADIO STOPPED IN AND CLARIFIED THE ALT AND VECTOR. ABOUT 1/2 WAY DOWN THE RWY I HEARD ANOTHER XMISSION, BUT IT WAS COMPLETELY GARBLED. I STATED 'UNREADABLE' IN RESPONSE. IMMEDIATELY AFTER TKOF, I SWITCHED OVER TO DEP. SHE ADVISED ME THAT WE DID NOT HAVE A TKOF CLRNC (THE ONE THING I WAS SURE I HAD HEARD). OBVIOUSLY, THE BIG ELEMENT HERE WAS THE ABYSMALLY BAD TWR RADIO. SECONDARILY, I SHOULD HAVE INSISTED ON A CLR XMISSION OF THE ENTIRE CLRNC, BUT -- AND THIS IS ALWAYS A PRACTICE THAT INCREASES PRESSURE TO GO ON A FLC -- WE HAD BEEN POSITIONED ON THE ACTIVE RWY FOR A CONSIDERABLE PERIOD OF TIME BY THEN. I KNOW FROM PERSONAL EXPERIENCE THAT BEING ON TWR CTL IS NO GUARANTEE THAT NO ONE WILL TRY TO LAND ON TOP OF YOU. SUPPLEMENTAL INFO FROM ACN 518097: WHEN RECEIVING OUR TAXI CLRNC FROM THE GND CTLR, I INFORMED HIM THAT HIS XMISSION WAS VERY BROKEN AND HARD TO UNDERSTAND. AFTER HE REPEATED THE CLRNC, I COULD UNDERSTAND IT ENOUGH TO REPEAT IT BACK TO HIM WITH HIS SATISFACTION. WE TAXIED TO THE HOLD LINE FOR RWY. WE WERE GIVEN POS AND WAIT ON RWY 6. WHILE IN POS, THE CTLR AMENDED OUR CLRNC WITH A NEW HDG OF 120 DEGS AND 3000 FT. I ASKED FOR VERIFICATION TWICE AND THE CAPT THEN ASKED FOR VERIFICATION AND WAS SATISFIED WITH HIS ANSWER. WE STARTED THE TKOF ROLL. WE SHOULD HAVE STAYED IN POS AND HAD THEM TRY ANOTHER XMITTER UNTIL WE COULD CLRLY UNDERSTAND THE TWR CTLR. THE SIT DID NOT SEEM TO CAUSE ANY DANGEROUS SIT OR A CONFLICT WITH ANY OTHER ACFT. BUT IT COULD HAVE.
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.