<< >> NASA ASRS Report 787373, May 2008

Phl controller experienced operational error at 6000 ft after assuming a climb to 10000 ft was issued when in fact it was not given and confliction developed.

Attributes
ACN	787373
Time
Date	200805
Local Time Of Day	0601 To 1200
Place
Locale Reference	airport : ptw.airport
State Reference	PA
Altitude	msl single value : 6000
Environment
Flight Conditions	IMC
Weather Elements	Rain
Light	Daylight
Aircraft 1
Controlling Facilities	tracon : phl.tracon artcc : zspd.artcc
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	departure : on vectors
Flight Plan	IFR
Aircraft 2
Controlling Facilities	tracon : phl.tracon
Operator	common carrier : air carrier
Make Model Name	A320
Operating Under FAR Part	Part 121
Flight Phase	descent : intermediate altitude
Route In Use	arrival : on vectors
Flight Plan	IFR
Person 1
Affiliation	government : faa
Function	controller : approach
Qualification	pilot : instrument
Experience	controller radar : 19 controller time certified in position1 : 12
ASRS Report	787373
Person 2
Affiliation	government : faa
Function	controller : radar
Qualification	controller : radar
Experience	controller radar : 18 controller time certified in position1 : 10
ASRS Report	786704
Events
Anomaly	conflict : airborne less severe non adherence : required legal separation
Independent Detector	atc equipment : conflict alert aircraft equipment : tcas other controllera
Resolutory Action	controller : issued alert controller : issued new clearance
Consequence	faa : investigated
Miss Distance	horizontal : 16800 vertical : 900
Supplementary
Problem Areas	ATC Human Performance
Primary Problem	ATC Human Performance
Air Traffic Incident	Operational Error

Narrative:

I was working a B737 from phl to first fix ptw from the phl (north departure) position. I climbed aircraft to 6000 ft to avoid traffic. Later turned aircraft to the ptw VOR and 'thought' I climbed the aircraft to 10000 ft. Aircraft crossed my boundary with phl (north arrival) position at 6000 ft and conflicted with A319 descending to 6000 ft. Supplemental information from acn 786704: I took the north departure position; with a briefing that the B737 was climbing to 10000 ft direct to ptw. I issued a climb to 13000 ft when I could; and thought the data block showed him out of 8000 ft. He reported out of 6000 ft for 13000 ft; then asked about traffic off his nose at 6500 ft.

Related reports:

• ZJX controller experienced operational error at 7000 ft when...

	Enter your search terms Submit search form
	Web www.37000feet.com

Original NASA ASRS Text

Title: PHL CTLR EXPERIENCED OPERROR AT 6000 FT AFTER ASSUMING A CLIMB TO 10000 FT WAS ISSUED WHEN IN FACT IT WAS NOT GIVEN AND CONFLICTION DEVELOPED.

Narrative: I WAS WORKING A B737 FROM PHL TO FIRST FIX PTW FROM THE PHL (N DEP) POS. I CLBED ACFT TO 6000 FT TO AVOID TFC. LATER TURNED ACFT TO THE PTW VOR AND 'THOUGHT' I CLBED THE ACFT TO 10000 FT. ACFT CROSSED MY BOUNDARY WITH PHL (N ARR) POS AT 6000 FT AND CONFLICTED WITH A319 DSNDING TO 6000 FT. SUPPLEMENTAL INFO FROM ACN 786704: I TOOK THE N DEP POS; WITH A BRIEFING THAT THE B737 WAS CLBING TO 10000 FT DIRECT TO PTW. I ISSUED A CLB TO 13000 FT WHEN I COULD; AND THOUGHT THE DATA BLOCK SHOWED HIM OUT OF 8000 FT. HE RPTED OUT OF 6000 FT FOR 13000 FT; THEN ASKED ABOUT TFC OFF HIS NOSE AT 6500 FT.

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.