37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 966881 |
Time | |
Date | 201108 |
Local Time Of Day | 1201-1800 |
Place | |
Locale Reference | ZZZ.Airport |
State Reference | US |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Make Model Name | SR22 |
Operating Under FAR Part | Part 91 |
Flight Phase | Takeoff |
Flight Plan | IFR |
Person 1 | |
Function | Pilot Flying Single Pilot |
Qualification | Flight Crew Commercial Flight Crew Multiengine Flight Crew Instrument |
Experience | Flight Crew Last 90 Days 35 Flight Crew Total 2260 Flight Crew Type 1700 |
Events | |
Anomaly | ATC Issue All Types Conflict Ground Conflict Less Severe Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy |
Narrative:
I was cleared to taxi to the runway. When approaching the hold short line for the runway I switched to the tower frequency. The tower controller called me to ask if I would be 'ready to go'. I answered I was ready and then the controller issued an instruction; which I misunderstood to mean I was cleared for take-off. He also added traffic would be landing on the other runway. I read back 'cleared for take-off; runway xx; will be looking for the traffic' and then proceeded to take-off from the runway. When I was climbing the controller told me I was expected to line up and wait because of a landing traffic on the other runway (an intersecting runway) and gave me a phone number to call when back on the ground. As far as I remember I did not hear him state 'line up and wait' - maybe he was cut-off or he pressed his mike after he had started to speak or I just plainly misunderstood him. I was (wrongly) convinced I was cleared for take-off and this is actually the instruction I repeated; but the controller did not catch my incorrect read-back. I believe the reason for the miscommunication is that I was really expecting to be cleared for take-off when the controller asked me if I was ready to go so close to the runway hold short line and my mind was already set. Also when he said there would be a landing traffic on the other runway I (wrongly) assumed the traffic would be landing well after I was airborne. In addition; the controller did not catch my incorrect read-back.
Original NASA ASRS Text
Title: An SR22 pilot took off without clearance because he misunderstood the Controller's command and was notified about his error by ATC once airborne.
Narrative: I was cleared to taxi to the runway. When approaching the hold short line for the runway I switched to the Tower frequency. The Tower Controller called me to ask if I would be 'ready to go'. I answered I was ready and then the Controller issued an instruction; which I misunderstood to mean I was cleared for take-off. He also added traffic would be landing on the other runway. I read back 'cleared for take-off; runway XX; will be looking for the traffic' and then proceeded to take-off from the runway. When I was climbing the Controller told me I was expected to line up and wait because of a landing traffic on the other runway (an intersecting runway) and gave me a phone number to call when back on the ground. As far as I remember I did not hear him state 'line up and wait' - maybe he was cut-off or he pressed his mike after he had started to speak or I just plainly misunderstood him. I was (wrongly) convinced I was cleared for take-off and this is actually the instruction I repeated; but the Controller did not catch my incorrect read-back. I believe the reason for the miscommunication is that I was really expecting to be cleared for take-off when the Controller asked me if I was ready to go so close to the runway hold short line and my mind was already set. Also when he said there would be a landing traffic on the other runway I (wrongly) assumed the traffic would be landing well after I was airborne. In addition; the Controller did not catch my incorrect read-back.
Data retrieved from NASA's ASRS site as of April 2012 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.