2009-09 · NASA ASRS report 853333
Air carrier departure from BOS described potential conflict when cleared for takeoff on Runway 22L with traffic on landing role on Runway 27; alleging ATC's anticipated separation was inappropriate.
We were cleared for takeoff on Runway 22L. When clearance was given an aircraft that had landed on Runway 27 was still 300 FT from our runway on the EAST SIDE!! The aircraft was either going through the intersection of Runways 22L and 27; or going through the intersection of Echo Taxiway and 22L (a runway incursion hot spot). The First Officer and I assumed the clearance for takeoff was for an aircraft on 22R (a Controller error) or a clearance for us to takeoff with an aircraft YET TO CROSS OUR RUNWAY (a Controller error). I deem this to be a runway incursion. Repeating our clearance was given BEFORE the aircraft landing made it even TO one of the above intersections. I questioned the takeoff clearance and was immediately told to expedite our takeoff because of traffic behind us on final to Runway 22L. we proceeded with a normal takeoff and then prior to our flaps up call BELOW 1000 FT; the Controller with extremely poor attitude rattled off the phone number for us to call when we landed. I believe this situation had the potential to be catastrophic had the aircraft that landed on Runway 27 been on the runway if we had proceeded with our takeoff with the initial clearance. The anticipated clearance that the Controllers may use in this situation (I do not believe) does not allow them to do what this Controller did and if it does -- it shouldn't and the practice should be immediately terminated. As I said; the Controller's attitude on the radio was poor after we questioned the situation in a professional way.
Cleared into position Runway 22L. We were told aircraft landing Runway 27. Controller issued takeoff clearance with other aircraft 100 yards prior to crossing Runway 22L (either on Runway 27 or Taxiway E). The aircraft was at speed where it could have stopped by Runway 22L. I was waiting to respond to the takeoff clearance until the aircraft was stopped or clear of Runway 22L. As the tail of the other aircraft cleared; the Controller gave another clearance for an 'immediate takeoff traffic on a 2 mile final' for our runway. The rest of the flight was uneventful. The aircraft behind us did not go around.
Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.
Loading the flight search…
Pick an aircraft model — Boeing 737, Airbus A320, A380, Boeing 787 Dreamliner and more — enter your origin airport, and FlightFinder shows every route that plane flies from there with live fares.
We support Boeing 737/747/757/767/777/787, the full Airbus A220/A319/A320/A321/A330/A340/A350/A380 family, Embraer E170/E175/E190/E195, Bombardier CRJ and Dash 8, and the ATR 42/72 turboprops.
Search and schedules are free. Pro ($4.99/month, $39/year, or $99 one-time lifetime) unlocks the enriched flight card — on-time stats, CO₂ per passenger, amenities, live gate & weather — plus My Trips with push alerts.
Live schedules come from Amadeus, AeroDataBox and Travelpayouts. Observed routes (which aircraft actually flew a given city pair) are crowdsourced from adsb.lol ADS-B data under the Open Database License.