 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Tower local controller issued takeoff clearance to a departing aircraft before an arriving aircraft landing on a crossing runway was clear of the departure runway.
| Attributes | |
| ACN | 140662 |
| Time | |
| Date | 199003 |
| Day | Fri |
| Local Time Of Day | 1201 To 1800 |
| Place | |
| Locale Reference | airport : mli |
| State Reference | IL |
| Altitude | agl bound lower : 0 agl bound upper : 0 |
| Environment | |
| Flight Conditions | VMC |
| Light | Dusk |
| Aircraft 1 | |
| Controlling Facilities | tower : mnl |
| Operator | common carrier : air carrier |
| Make Model Name | Medium Transport, High Wing, 2 Turboprop Eng |
| Flight Phase | climbout : takeoff |
| Flight Plan | IFR |
| Aircraft 2 | |
| Operator | general aviation : corporate |
| Make Model Name | Small Transport, Low Wing, 2 Turbojet Eng |
| Flight Phase | ground other : taxi landing other |
| Flight Plan | VFR |
| Person 1 | |
| Affiliation | government : faa |
| Function | observation : observer |
| Qualification | controller : non radar |
| ASRS Report | 140662 |
| Person 2 | |
| Affiliation | government : faa |
| Function | controller : local |
| Qualification | controller : non radar |
| Events | |
| Anomaly | conflict : ground less severe non adherence : published procedure non adherence : required legal separation |
| Independent Detector | other controllera |
| Resolutory Action | none taken : anomaly accepted |
| Consequence | Other |
| Miss Distance | horizontal : 3800 |
| Supplementary | |
| Primary Problem | ATC Human Performance |
| Air Traffic Incident | Operational Error |
Narrative:
Aircraft X started takeoff roll runway 27, while the second aircraft Y was in the intersection of runway 27 and runway 23, having landed runway 23. I observed this from the cockpit jump seat of the aircraft X. Aircraft Y rolled through the intersection and the aircraft X continued takeoff west/O further incident. The takeoff clearance had been issued prematurely; no action was taken to correct the situation. I believe the situation occurred because the controller planned to depart aircraft X prior to the arrival of aircraft Y on runway 23. However, that was not accomplished due to other traffic on runway 23. Another aircraft was approaching to land runway 27, which forced the controller to rush the takeoff clearance. This type of situation rarely happens unintentionally--rather, it is called 'anticipated sep,' even though FAA handbook 7110.65 prohibits it. Simply stated, it's cheating.
Original NASA ASRS Text
Title: TWR LCL CTLR ISSUED TKOF CLRNC TO A DEPARTING ACFT BEFORE AN ARRIVING ACFT LNDG ON A CROSSING RWY WAS CLEAR OF THE DEP RWY.
Narrative: ACFT X STARTED TKOF ROLL RWY 27, WHILE THE SECOND ACFT Y WAS IN THE INTXN OF RWY 27 AND RWY 23, HAVING LANDED RWY 23. I OBSERVED THIS FROM THE COCKPIT JUMP SEAT OF THE ACFT X. ACFT Y ROLLED THROUGH THE INTXN AND THE ACFT X CONTINUED TKOF W/O FURTHER INCIDENT. THE TKOF CLRNC HAD BEEN ISSUED PREMATURELY; NO ACTION WAS TAKEN TO CORRECT THE SITUATION. I BELIEVE THE SITUATION OCCURRED BECAUSE THE CTLR PLANNED TO DEPART ACFT X PRIOR TO THE ARR OF ACFT Y ON RWY 23. HOWEVER, THAT WAS NOT ACCOMPLISHED DUE TO OTHER TFC ON RWY 23. ANOTHER ACFT WAS APCHING TO LAND RWY 27, WHICH FORCED THE CTLR TO RUSH THE TKOF CLRNC. THIS TYPE OF SITUATION RARELY HAPPENS UNINTENTIONALLY--RATHER, IT IS CALLED 'ANTICIPATED SEP,' EVEN THOUGH FAA HANDBOOK 7110.65 PROHIBITS IT. SIMPLY STATED, IT'S CHEATING.
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.