IAH Local Controller described loss of separation event involving a departure and arrival aircraft; reporter claiming complexity was an issue as was the expectation to maximize arrival/departure traffic.
Synopsis
IAH Local Controller described loss of separation event involving a departure and arrival aircraft; reporter claiming complexity was an issue as was the expectation to maximize arrival/departure traffic.
Narrative
Complexity was an issue. Was instructed to hit departure holes on Local Center (Runway 26L) to keep delays to a minimum. Aircraft taxiing out were told to expect either Runway 26L or 26R as their departure runway. Traffic on final were conducting visual approaches (weather clear and no ceiling); Aircraft X was told to taxi into position and hold Rwy 26L and advised of traffic 3 to 4 mile final landing Runway 26L. Previous landing aircraft taxied off high speed taxiway and Aircraft X was cleared for immediate takeoff and reissued traffic on final that was 2 1/2 mile final. Aircraft X was slow to role probably due to weight. Aircraft X was issued traffic of the expected departure and continued his approach to Runway 26L. By the time Aircraft Y crossed the landing threshold of Runway 26L it appeared that Aircraft X's nose wheel gear had rotated yet Aircraft X was approximately 6000 feet from approach end threshold. Recommendation; don't deviate from our normal departure flow of departures to Runway 15L/R. Normal flow at IAH works fine having our departures taxi to either Rwy 15L/R; however; because of the delay issue sometimes IAH feels pressed to depart Runway 26L or Runway 26R and land Runway 26L and Runway 27; which creates a crossing scenario that is unsafe as well. I recommend that if we need to add an additional departure runway (i.e.; Runway 26L) then we land only Runway 26R and Runway 27 because it is safer to cross the departure end of a takeoff runway than to hit arrival holes with departures or runway crossings. Also having visual distance landmarks that can be seen from Tower would aid in determining runway distance if and when we are required to hit departure holes. At this time all information is stored in a book binder and can not be readily accessed for quick observation. Having the information under plexiglass on the positions where it can be seen readily; is by far better and more user friendly than looking through an Air Traffic Binder.
Second reporter narrative
Aircraft X on departure roll with Aircraft Y on short final. This proximity is what caught my attention. I (FLM) told the Local Controller that it did not look good. I did not instruct him to send aircraft around. Aircraft Y landed with what appeared to be less than required separation. Recommendation; be more proactive with what in my opinion are unsafe operations. Coach the controllers on timely and safer decision making. Have a more black and white cut off as to when to send aircraft around on questionable situations.
More incidents for this aircraft family →
Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.