Narrative:

I phoned mia FSS for a standard preflight briefing and to file an international IFR flight plan. The briefer was uncertain about an impending tfr involving my flight and suggested I call in the morning. In the morning; I phoned mia FSS for an abbreviated preflight briefing and was told that the tfr was scheduled to begin at XS43Z. At XA32 departed and called dab approach control. I was given a squawk code; vectors to V3 and 11000 ft altitude. When I questioned the changes (not 'amendments') I was told I would be 'given vectors later.' also; the 11000 ft altitude was unusual since controllers assign florida sbound IFR aircraft to 'even' altitudes until offshore. When I changed to orl approach control; I received the standard barometric reading; but after 5 mins or so; orl asked; 'when are you going to turn to comet?' comet was the first intersection of my original IFR flight plan. When I questioned this; I was told to 'resume your own navigation.' I called again for an explanation and was told to change to miami. After reporting to miami control; I was asked if I 'would accept 13000 ft' followed by to neube intersection; not comet. I understood that I was assigned to neube and began a climb to 13000 ft. The miami controller informed me that her call was a question and not an assigned altitude; but almost immediately I was given the 13000 ft altitude. No other aircraft were involved in this incident. At XG34; I received a phone call from the FAA who informed me that I committed a 'pilot deviation.' I believe that this misunderstanding resulted when the controller coupling a proposed altitude with an assigned intersection. The proposed altitude (13000 ft) was assigned moments later. I understand that controllers are busy; but today demonstrated how hard it is for them to keep everything straight.

Related reports:

Google
 

Original NASA ASRS Text

Title: BE33 PILOT REPORTS CONFUSION OVER A CLEARANCE TO CLIMB TO 13000 FEET WHICH WAS ACTUALLY A QUESTION OF CAN YOU ACCEPT 13000 FEET.

Narrative: I PHONED MIA FSS FOR A STANDARD PREFLT BRIEFING AND TO FILE AN INTL IFR FLT PLAN. THE BRIEFER WAS UNCERTAIN ABOUT AN IMPENDING TFR INVOLVING MY FLT AND SUGGESTED I CALL IN THE MORNING. IN THE MORNING; I PHONED MIA FSS FOR AN ABBREVIATED PREFLT BRIEFING AND WAS TOLD THAT THE TFR WAS SCHEDULED TO BEGIN AT XS43Z. AT XA32 DEPARTED AND CALLED DAB APCH CTL. I WAS GIVEN A SQUAWK CODE; VECTORS TO V3 AND 11000 FT ALT. WHEN I QUESTIONED THE CHANGES (NOT 'AMENDMENTS') I WAS TOLD I WOULD BE 'GIVEN VECTORS LATER.' ALSO; THE 11000 FT ALT WAS UNUSUAL SINCE CTLRS ASSIGN FLORIDA SBOUND IFR ACFT TO 'EVEN' ALTS UNTIL OFFSHORE. WHEN I CHANGED TO ORL APCH CTL; I RECEIVED THE STANDARD BAROMETRIC READING; BUT AFTER 5 MINS OR SO; ORL ASKED; 'WHEN ARE YOU GOING TO TURN TO COMET?' COMET WAS THE FIRST INTXN OF MY ORIGINAL IFR FLT PLAN. WHEN I QUESTIONED THIS; I WAS TOLD TO 'RESUME YOUR OWN NAV.' I CALLED AGAIN FOR AN EXPLANATION AND WAS TOLD TO CHANGE TO MIAMI. AFTER RPTING TO MIAMI CTL; I WAS ASKED IF I 'WOULD ACCEPT 13000 FT' FOLLOWED BY TO NEUBE INTXN; NOT COMET. I UNDERSTOOD THAT I WAS ASSIGNED TO NEUBE AND BEGAN A CLB TO 13000 FT. THE MIAMI CTLR INFORMED ME THAT HER CALL WAS A QUESTION AND NOT AN ASSIGNED ALT; BUT ALMOST IMMEDIATELY I WAS GIVEN THE 13000 FT ALT. NO OTHER ACFT WERE INVOLVED IN THIS INCIDENT. AT XG34; I RECEIVED A PHONE CALL FROM THE FAA WHO INFORMED ME THAT I COMMITTED A 'PLTDEV.' I BELIEVE THAT THIS MISUNDERSTANDING RESULTED WHEN THE CTLR COUPLING A PROPOSED ALT WITH AN ASSIGNED INTXN. THE PROPOSED ALT (13000 FT) WAS ASSIGNED MOMENTS LATER. I UNDERSTAND THAT CTLRS ARE BUSY; BUT TODAY DEMONSTRATED HOW HARD IT IS FOR THEM TO KEEP EVERYTHING STRAIGHT.

Data retrieved from NASA's ASRS site as of May 2009 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.