37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1310716 |
Time | |
Date | 201511 |
Local Time Of Day | 1801-2400 |
Place | |
Locale Reference | ORD.Airport |
State Reference | IL |
Environment | |
Light | Dusk |
Aircraft 1 | |
Make Model Name | Large Transport |
Operating Under FAR Part | Part 121 |
Flight Phase | Takeoff |
Flight Plan | IFR |
Aircraft 2 | |
Operating Under FAR Part | Part 129 |
Flight Phase | Initial Climb |
Flight Plan | IFR |
Person 1 | |
Function | Local |
Qualification | Air Traffic Control Fully Certified |
Experience | Air Traffic Control Time Certified In Pos 1 (mon) .4 |
Events | |
Anomaly | ATC Issue All Types Conflict Ground Conflict Less Severe Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy Inflight Event / Encounter Weather / Turbulence |
Narrative:
Aircraft Y departed 28R; special request. I had to get him out in an arrival gap. Aircraft X was in position on 28C. I waited until I had 5 miles with both aircraft before launching aircraft X for the wake. Then before aircraft X started rolling another controller said 'you know you need 3 minutes'. I forgot that this operation was considered an intersection departure from the same runway.aircraft X did not start departure roll. I cancelled his takeoff clearance; but I got no response and aircraft X started their departure. I figured since it was not safety critical and we had a 35-40 kt wind out of the south. I decided not to reiterate instructions to stop aircraft X. I did not want a brake fire or anything of the sort. I believe wake turbulence was not a factor due to the high winds. I had about 7 miles between aircraft after aircraft X got airborne. I decided that safety was not an issue. I felt stopping the aircraft X on the runway would of been the lesser desired scenario.I forgot about the 3 min rule. I think this was my second time as [a] full performance level (fpl) departing 28C. The winds were very strong out of the south which made us use rarely used runway configurations.no recommendations - I just needed to remember the 3 min rule.
Original NASA ASRS Text
Title: An ORD Local Controller reported of departing an aircraft and not having the required 3 minute separation. The reporter did attempt to stop the departing aircraft but aircraft did not stop. The Controller thought it was ok to let the departure continue due to the winds at the airport. The Controller forgot the operation was considered an intersection departure.
Narrative: Aircraft Y departed 28R; special request. I had to get him out in an arrival gap. Aircraft X was in position on 28C. I waited until I had 5 miles with both aircraft before launching Aircraft X for the wake. Then before Aircraft X started rolling another controller said 'You know you need 3 minutes'. I forgot that this operation was considered an intersection departure from the same runway.Aircraft X did not start departure roll. I cancelled his takeoff clearance; but I got no response and Aircraft X started their departure. I figured since it was not safety critical and we had a 35-40 kt wind out of the south. I decided not to reiterate instructions to stop Aircraft X. I did not want a brake fire or anything of the sort. I believe wake turbulence was not a factor due to the high winds. I had about 7 miles between aircraft after Aircraft X got airborne. I decided that safety was not an issue. I felt stopping the Aircraft X on the runway would of been the lesser desired scenario.I forgot about the 3 min rule. I think this was my second time as [a] Full Performance Level (FPL) departing 28C. The winds were very strong out of the south which made us use rarely used runway configurations.No recommendations - I just needed to remember the 3 min rule.
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.