Narrative:

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.

Google
 

Original NASA ASRS Text

Title: 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.

Narrative: 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.

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