 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Air carrier departure from dca elected to continue take off because of V1 speed even though an abort instruction was issued by ATC because of a slow exiting previous landing aircraft.
| Attributes | |
| ACN | 1064264 |
| Time | |
| Date | 201301 |
| Local Time Of Day | 1201-1800 |
| Place | |
| Locale Reference | DCA.Airport |
| State Reference | DC |
| Environment | |
| Flight Conditions | VMC |
| Aircraft 1 | |
| Make Model Name | EMB ERJ 145 ER/LR |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Takeoff |
| Aircraft 2 | |
| Make Model Name | Commercial Fixed Wing |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Taxi |
| Person 1 | |
| Function | Pilot Flying Captain |
| Qualification | Flight Crew Air Transport Pilot (ATP) |
| Person 2 | |
| Function | Pilot Not Flying First Officer |
| Events | |
| Anomaly | ATC Issue All Types Deviation - Procedural Clearance Ground Incursion Runway |
Narrative:
Air carrier X had just landed runway 19 in dca. We were cleared to line up and wait. Air carrier X was exiting the runway and we were cleared for take off. As soon as we could visually see air carrier X was clear of runway 19 we started to depart. For whatever reason; air carrier X decided to stop immediately after their aircraft cleared the runway however it was still showing an alert on the ground surveillance radar in ATC because they did not pull off far enough. ATC told us to abort take off; but we were already at V1 and had insufficient runway to reject the take off. We continued without incident and there was never any question on separation. When we landed; I spoke to the tower supervisor who indicated that it was not our fault in anyway. He also stated that they had the separation with air carrier X and they believe it was a malfunction of the electronic runway incursion system. ATC should make sure that all aircraft pull completely off the active runway before issuing a take off clearance.
Original NASA ASRS Text
Title: Air Carrier departure from DCA elected to continue take off because of V1 speed even though an abort instruction was issued by ATC because of a slow exiting previous landing aircraft.
Narrative: Air Carrier X had just landed Runway 19 in DCA. We were cleared to line up and wait. Air Carrier X was exiting the runway and we were cleared for take off. As soon as we could visually see Air Carrier X was clear of Runway 19 we started to depart. For whatever reason; Air Carrier X decided to stop immediately after their aircraft cleared the runway however it was still showing an alert on the ground surveillance RADAR in ATC because they did not pull off far enough. ATC told us to abort take off; but we were already at V1 and had insufficient runway to reject the take off. We continued without incident and there was never any question on separation. When we landed; I spoke to the Tower Supervisor who indicated that it was not our fault in anyway. He also stated that they had the separation with Air Carrier X and they believe it was a malfunction of the electronic runway incursion system. ATC should make sure that all aircraft pull completely off the active runway before issuing a take off clearance.
Data retrieved from NASA's ASRS site as of July 2013 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.