Multiple runway operation parallel runways, air carrier X had near midair collision, less than standard separation from air carrier Y departing on parallel runway. System error. Evasive action taken.

Home

Browse by month

Random

Latest

About

Contact

Attributes
ACN	297684
Time
Date	199502
Day	Mon
Local Time Of Day	1201 To 1800
Place
Locale Reference	atc facility : clt
State Reference	NC
Altitude	agl bound lower : 600 agl bound upper : 600
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	tower : clt
Operator	common carrier : air carrier
Make Model Name	Shorts SD-360
Operating Under FAR Part	Part 121
Flight Phase	climbout : initial
Route In Use	enroute : on vectors
Flight Plan	IFR
Aircraft 2
Operator	common carrier : air carrier
Make Model Name	F28 Undifferentiated or Other Model
Operating Under FAR Part	Part 121
Navigation In Use	Other
Flight Phase	climbout : initial
Flight Plan	IFR
Person 1
Affiliation	government : faa
Function	controller : local
Qualification	controller : radar
Experience	controller non radar : 4 controller radar : 8
ASRS Report	297684
Person 2
Affiliation	government : faa
Function	controller : local
Qualification	controller : radar
Events
Anomaly	conflict : nmac non adherence : published procedure non adherence : required legal separation
Independent Detector	other controllera other flight crewa
Resolutory Action	flight crew : took evasive action
Consequence	faa : investigated
Miss Distance	horizontal : 200 vertical : 100
Supplementary
Primary Problem	ATC Human Performance
Air Traffic Incident	Operational Error Intra Facility Coordination Failure

Narrative:

I was working local control east, when ground taxied a SHD6 X to runway 18L for a wbound departure. I requested a release from local control west for a 270 degree heading and approval was given. I cleared the SHD6 for takeoff to fly a 270 degree heading. I watched the SHD6 start a right turn, started to say contact departure, when I saw a FK28 Y rotating on runway 18R south of mid field. I issued traffic, 12 O'clock departing parallel runway, no factor, it appeared to me as though the SHD6 would pass behind the FK28). The SHD6 pilot took evasive action -- a left turn paralleling the jet departure. The local west controller, I had forgotten about the traffic released on the parallel runway, and launched a departure which conflicted with the SHD6. Routinely, at charlotte, aircraft are taxied to runways for convenience of the operator to save taxi times, as in this situation. This could have been prevented by using a runway that procedures state, additionally, if a visual reminder was in place to warn the local control west (or remind) of the released aircraft.

Original NASA ASRS Text

Title: MULTIPLE RWY OP PARALLEL RWYS, ACR X HAD NMAC, LTSS FROM ACR Y DEPARTING ON PARALLEL RWY. SYS ERROR. EVASIVE ACTION TAKEN.

Narrative: I WAS WORKING LCL CTL E, WHEN GND TAXIED A SHD6 X TO RWY 18L FOR A WBOUND DEP. I REQUESTED A RELEASE FROM LCL CTL W FOR A 270 DEG HDG AND APPROVAL WAS GIVEN. I CLRED THE SHD6 FOR TKOF TO FLY A 270 DEG HDG. I WATCHED THE SHD6 START A R TURN, STARTED TO SAY CONTACT DEP, WHEN I SAW A FK28 Y ROTATING ON RWY 18R S OF MID FIELD. I ISSUED TFC, 12 O'CLOCK DEPARTING PARALLEL RWY, NO FACTOR, IT APPEARED TO ME AS THOUGH THE SHD6 WOULD PASS BEHIND THE FK28). THE SHD6 PLT TOOK EVASIVE ACTION -- A L TURN PARALLELING THE JET DEP. THE LCL W CTLR, I HAD FORGOTTEN ABOUT THE TFC RELEASED ON THE PARALLEL RWY, AND LAUNCHED A DEP WHICH CONFLICTED WITH THE SHD6. ROUTINELY, AT CHARLOTTE, ACFT ARE TAXIED TO RWYS FOR CONVENIENCE OF THE OPERATOR TO SAVE TAXI TIMES, AS IN THIS SIT. THIS COULD HAVE BEEN PREVENTED BY USING A RWY THAT PROCS STATE, ADDITIONALLY, IF A VISUAL REMINDER WAS IN PLACE TO WARN THE LCL CTL W (OR REMIND) OF THE RELEASED ACFT.

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.