Msy controller describes a situation where he climbed an A319 aircraft through the wake of a B757 an...

Attributes
ACN	1203838
Time
Date	201409
Local Time Of Day	1201-1800
Place
Locale Reference	MSY.Airport
State Reference	LA
Environment
Light	Daylight
Aircraft 1
Make Model Name	B757-200
Operating Under FAR Part	Part 121
Flight Phase	Cruise
Route In Use	Vectors
Flight Plan	IFR
Aircraft 2
Make Model Name	A319
Operating Under FAR Part	Part 121
Flight Phase	Climb
Route In Use	Vectors
Flight Plan	IFR
Person 1
Function	Trainee
Qualification	Air Traffic Control Developmental
Events
Anomaly	ATC Issue All Types Deviation - Procedural Published Material / Policy Deviation - Procedural Clearance Inflight Event / Encounter Wake Vortex Encounter

Narrative:

Aircraft X; was set up in a left downwind to runway 10 level at FL100; heading 270 degrees. Aircraft Y; had just departed runway 10 and turned north bound climbing to FL090; heading 010 degrees. Aircraft X had passed the flight path of aircraft Y's assigned heading; traffic was called to aircraft Y; who called aircraft X in sight. Aircraft X had already passed through the flight path of aircraft Y by a couple of miles; so I did not tell the pilot of aircraft Y to maintain visual separation; as their flight paths had already crossed. I told the pilot of aircraft Y caution wake turbulence; and climbed him to FL150. The event happened because of residual wake turbulence behind aircraft X and because I didn't either let aircraft Y level and wait until the aircraft crossed the wake turbulence zone; or because I didn't tell the pilot of aircraft Y to maintain visual separation from aircraft X; which had already crossed aircraft Y's flight path.perhaps a cedar briefing item as just a reminder about residual wake turbulence trails of heavy aircraft.

Original NASA ASRS Text

Title: MSY Controller describes a situation where he climbed an A319 aircraft through the wake of a B757 and didn't use the residual wake turbulence rules for proper separation.

Narrative: Aircraft X; was set up in a left downwind to Runway 10 level at FL100; heading 270 degrees. Aircraft Y; had just departed Runway 10 and turned north bound climbing to FL090; heading 010 degrees. Aircraft X had passed the flight path of Aircraft Y's assigned heading; traffic was called to Aircraft Y; who called Aircraft X in sight. Aircraft X had already passed through the flight path of Aircraft Y by a couple of miles; so I did not tell the pilot of Aircraft Y to maintain visual separation; as their flight paths had already crossed. I told the pilot of Aircraft Y caution wake turbulence; and climbed him to FL150. The event happened because of residual wake turbulence behind Aircraft X and because I didn't either let Aircraft Y level and wait until the aircraft crossed the wake turbulence zone; or because I didn't tell the pilot of Aircraft Y to maintain visual separation from Aircraft X; which had already crossed Aircraft Y's flight path.Perhaps a Cedar briefing item as just a reminder about residual wake turbulence trails of Heavy aircraft.

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

Msy controller describes a situation where he climbed an A319 aircraft through the wake of a B757 and didn't use the residual wake turbulence rules for proper separation.