37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 517930 |
Time | |
Date | 200107 |
Day | Sun |
Local Time Of Day | 1201 To 1800 |
Place | |
Locale Reference | airport : bkl.airport |
State Reference | OH |
Altitude | agl single value : 0 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Operator | general aviation : personal |
Make Model Name | Skyhawk 172/Cutlass 172 |
Flight Phase | landing : roll landing : touch and go |
Flight Plan | None |
Person 1 | |
Affiliation | other |
Function | flight crew : single pilot |
Qualification | pilot : instrument pilot : cfi |
Experience | flight time last 90 days : 9 flight time total : 485 flight time type : 350 |
ASRS Report | 517930 |
Events | |
Anomaly | non adherence : published procedure non adherence : clearance non adherence : far other anomaly other |
Resolutory Action | 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:
I contacted burke (bkl) tower initially, 10 mi east. After contact was established, I said I had the information and requested 1 touch-and-go landing. Going to cgf (about 8 mi away) for a full stop, I was asked to report 5 mi east. When I reported, I was told to report a 2 mi final for runway 24R. When I reported, I was immediately cleared to land runway 24R. Immediately after doing the touch-and-go, the controller stated (in an obviously annoyed voice), 'aircraft xyz, you were cleared to land runway 24R.' I was surprised, but stated that I had landed runway 24R. He came back to say 'that means full-stop and taxi to the ramp.' I immediately realized I had not been cleared for the touch-and-go. The environment was very busy (I was pleasantly surprised when he said to report 5 mi, as I was taking my son up for a brief ride). After the touch-and-go, the controller asked for my intentions (which had already been stated). While I clearly missed that I had not been cleared for the touch-and-go, generally I expect the controller to state 'unable' if traffic is too heavy. My initial request was very clear.
Original NASA ASRS Text
Title: A C172 PLT MADE A TOUCH-AND-GO AT BKL WITHOUT PERMISSION.
Narrative: I CONTACTED BURKE (BKL) TWR INITIALLY, 10 MI E. AFTER CONTACT WAS ESTABLISHED, I SAID I HAD THE INFO AND REQUESTED 1 TOUCH-AND-GO LNDG. GOING TO CGF (ABOUT 8 MI AWAY) FOR A FULL STOP, I WAS ASKED TO RPT 5 MI E. WHEN I RPTED, I WAS TOLD TO RPT A 2 MI FINAL FOR RWY 24R. WHEN I RPTED, I WAS IMMEDIATELY CLRED TO LAND RWY 24R. IMMEDIATELY AFTER DOING THE TOUCH-AND-GO, THE CTLR STATED (IN AN OBVIOUSLY ANNOYED VOICE), 'ACFT XYZ, YOU WERE CLRED TO LAND RWY 24R.' I WAS SURPRISED, BUT STATED THAT I HAD LANDED RWY 24R. HE CAME BACK TO SAY 'THAT MEANS FULL-STOP AND TAXI TO THE RAMP.' I IMMEDIATELY REALIZED I HAD NOT BEEN CLRED FOR THE TOUCH-AND-GO. THE ENVIRONMENT WAS VERY BUSY (I WAS PLEASANTLY SURPRISED WHEN HE SAID TO RPT 5 MI, AS I WAS TAKING MY SON UP FOR A BRIEF RIDE). AFTER THE TOUCH-AND-GO, THE CTLR ASKED FOR MY INTENTIONS (WHICH HAD ALREADY BEEN STATED). WHILE I CLRLY MISSED THAT I HAD NOT BEEN CLRED FOR THE TOUCH-AND-GO, GENERALLY I EXPECT THE CTLR TO STATE 'UNABLE' IF TFC IS TOO HVY. MY INITIAL REQUEST WAS VERY CLR.
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.