Cpr small transport climbed to 11000 and conflicted with another aircraft at that altitude. Less than standard separation even though controller vectored and descended the light transport.

Home

Browse by month

Random

Latest

About

Contact

Attributes
ACN	94234
Time
Date	198809
Day	Tue
Local Time Of Day	1201 To 1800
Place
Locale Reference	atc facility : rmg
State Reference	GA
Altitude	msl bound lower : 10000 msl bound upper : 11000
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	artcc : ztl
Operator	general aviation : corporate
Make Model Name	Small Transport, Low Wing, 2 Turboprop Eng
Flight Phase	climbout : intermediate altitude cruise other
Route In Use	enroute : on vectors
Flight Plan	IFR
Aircraft 2
Make Model Name	Any Unknown or Unlisted Aircraft Manufacturer
Flight Phase	cruise other
Flight Plan	IFR
Person 1
Affiliation	Other
Function	flight crew : single pilot
Qualification	pilot : cfi pilot : commercial pilot : instrument
Experience	flight time last 90 days : 60 flight time total : 12000 flight time type : 40
ASRS Report	94234
Person 2
Affiliation	government : faa
Function	controller : departure
Qualification	controller : radar
Events
Anomaly	altitude deviation : overshoot conflict : airborne less severe non adherence : required legal separation
Independent Detector	other controllera
Resolutory Action	controller : issued new clearance none taken : insufficient time
Consequence	faa : reviewed incident with flight crew faa : investigated
Miss Distance	horizontal : 15000 vertical : 0
Supplementary
Primary Problem	ATC Human Performance
Air Traffic Incident	Operational Error

Narrative:

Departed 8a4 radar vectors to gad. I had changed sectors (frequencys) several times. I had reported on the west low altitude frequency climbing to 11000'. This transmission was acknowledged by the controller, and at this time I requested a higher altitude and the controller replied he would have a climb in 20 mi and to maintain 11000'. Then he got excited and said I should have been at 10000', turned me left and descend to 10000'. He asked me to call him, which I did. The supervisor advised me that a system error had occurred and he would file a proposed pilot deviation with FSDO if the situation warranted. My position is that I was assigned 11000' and had reported climbing to that altitude on several previous xmissions. Callback conversation with reporter revealed the following. Reporter states that he has heard nothing further from ATC or FSDO. Feels strongly that he was at correct assigned altitude.

Original NASA ASRS Text

Title: CPR SMT CLIMBED TO 11000 AND CONFLICTED WITH ANOTHER ACFT AT THAT ALT. LESS THAN STANDARD SEPARATION EVEN THOUGH CTLR VECTORED AND DESCENDED THE LTT.

Narrative: DEPARTED 8A4 RADAR VECTORS TO GAD. I HAD CHANGED SECTORS (FREQS) SEVERAL TIMES. I HAD RPTED ON THE W LOW ALT FREQ CLBING TO 11000'. THIS XMISSION WAS ACKNOWLEDGED BY THE CTLR, AND AT THIS TIME I REQUESTED A HIGHER ALT AND THE CTLR REPLIED HE WOULD HAVE A CLB IN 20 MI AND TO MAINTAIN 11000'. THEN HE GOT EXCITED AND SAID I SHOULD HAVE BEEN AT 10000', TURNED ME LEFT AND DSND TO 10000'. HE ASKED ME TO CALL HIM, WHICH I DID. THE SUPVR ADVISED ME THAT A SYS ERROR HAD OCCURRED AND HE WOULD FILE A PROPOSED PLT DEV WITH FSDO IF THE SITUATION WARRANTED. MY POS IS THAT I WAS ASSIGNED 11000' AND HAD RPTED CLBING TO THAT ALT ON SEVERAL PREVIOUS XMISSIONS. CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING. RPTR STATES THAT HE HAS HEARD NOTHING FURTHER FROM ATC OR FSDO. FEELS STRONGLY THAT HE WAS AT CORRECT ASSIGNED ALT.

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