Reported loss of separation when an air carrier was climbed through the altitude of a military P3 at...

Attributes
ACN	385696
Time
Date	199711
Day	Fri
Local Time Of Day	1801 To 2400
Place
Locale Reference	atc facility : bkw
State Reference	WV
Altitude	msl bound lower : 26000 msl bound upper : 27000
Environment
Light	Night
Aircraft 1
Controlling Facilities	artcc : zdc
Operator	common carrier : air carrier
Make Model Name	B737 Undifferentiated or Other Model
Operating Under FAR Part	Part 121
Flight Phase	climbout : intermediate altitude
Route In Use	enroute : on vectors
Flight Plan	IFR
Aircraft 2
Operator	other
Make Model Name	Orion (P3)
Operating Under FAR Part	other : other
Flight Phase	cruise other
Person 1
Affiliation	government : faa
Function	controller : flight data
Qualification	controller : radar
ASRS Report	385696
Person 2
Affiliation	government : faa
Function	controller : radar
Qualification	controller : radar
ASRS Report	385791
Events
Anomaly	conflict : airborne less severe non adherence : required legal separation non adherence : published procedure other anomaly other
Independent Detector	aircraft equipment other aircraft equipment : unspecified
Resolutory Action	flight crew : took evasive action
Consequence	Other
Miss Distance	horizontal : 18000 vertical : 700
Supplementary
Primary Problem	ATC Human Performance
Air Traffic Incident	Operational Error

Narrative:

The 5 mi separation was lost between an air carrier B737 and a military P3 in the positive control area at the marlinton sector at ZDC. Separation was lost when the controller climbed the air carrier flight through the altitude of the military P3. The controller had just assumed the position which was likely a contributing factor. Callback conversation with reporter revealed the following information: the primary reporter was working the 'D' side, and the air carrier was thought to be a B737. Supplemental information from acn 385791: aircraft #1 instructed to maintain FL260. Aircraft #1 advised responding to TCASII. Aircraft #2 called aircraft #1 in sight. Controller had just taken the sector and second member of radar team occupied with other duties. Controller #2 unable to warn controller #1 in time to avoid less than standard separation. Controller #1 not 'up to speed' mentally on this particular scenario.

Original NASA ASRS Text

Title: RPTED LOSS OF SEPARATION WHEN AN ACR WAS CLBED THROUGH THE ALT OF A MIL P3 AT FL260.

Narrative: THE 5 MI SEPARATION WAS LOST BTWN AN ACR B737 AND A MIL P3 IN THE PCA AT THE MARLINTON SECTOR AT ZDC. SEPARATION WAS LOST WHEN THE CTLR CLBED THE ACR FLT THROUGH THE ALT OF THE MIL P3. THE CTLR HAD JUST ASSUMED THE POS WHICH WAS LIKELY A CONTRIBUTING FACTOR. CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING INFO: THE PRIMARY RPTR WAS WORKING THE 'D' SIDE, AND THE ACR WAS THOUGHT TO BE A B737. SUPPLEMENTAL INFO FROM ACN 385791: ACFT #1 INSTRUCTED TO MAINTAIN FL260. ACFT #1 ADVISED RESPONDING TO TCASII. ACFT #2 CALLED ACFT #1 IN SIGHT. CTLR HAD JUST TAKEN THE SECTOR AND SECOND MEMBER OF RADAR TEAM OCCUPIED WITH OTHER DUTIES. CTLR #2 UNABLE TO WARN CTLR #1 IN TIME TO AVOID LTSS. CTLR #1 NOT 'UP TO SPD' MENTALLY ON THIS PARTICULAR SCENARIO.

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.

Reported loss of separation when an air carrier was climbed through the altitude of a military P3 at FL260.