ASN Wikibase Occurrence # 314212
This information is added by users of ASN. Neither ASN nor the Flight Safety Foundation are responsible for the completeness or correctness of this information.
If you feel this information is incomplete or incorrect, you can submit corrected information.
| Date: | Friday 29 January 2016 |
| Time: | 08:05 LT |
| Type: |  Airbus A321-231 |
| Owner/operator: | Spirit Airlines |
| Registration: | N587NK |
| MSN: | 2476 |
| Year of manufacture: | 2005 |
| Engine model: | IAE V2533-A5 |
| Fatalities: | Fatalities: 0 / Occupants: |
| Aircraft damage: | None |
| Category: | Serious incident |
| Location: | Fort Lauderdale International Airport, FL (FLL/KFLL) -
 United States of America
|
| Phase: | Take off |
| Nature: | Unknown |
| Departure airport: | Fort Lauderdale International Airport, FL (FLL/KFLL) |
| Aguadilla-Rafael Hernández Airport (BQN/TJBQ) | |
| Investigating agency: | NTSB |
| Confidence Rating: |  Accident investigation report completed and information captured |
The runway incursion occurred during the early morning hours when traffic was light, and when the airport authority usually conducted maintenance activities on the airfield. The air traffic controller approved a request by an airport maintenance vehicle to operate on the runway; however, there were no standard operating procedures or standard phraseology regarding how airfield vehicle operators were to reference the specific runway end when requesting permission to enter a runway. This lack of standard procedure resulted in four hear back/read back errors between the operator of the vehicle and the air traffic controller immediately prior to the runway incursion event.
After the airport vehicle had been approved by the air traffic controller to operate on the runway, the crew of the A321 requested a clearance to taxi to the same runway for departure and was subsequently cleared for takeoff. The airport runways and taxiways were equipped with the Runway Status Light (RWSL) system. As the crew of the A321 aligned with the runway centerline for departure, the Takeoff Hold Lights (THL) portion of the RWSL activated, displaying red lights on the runway surface. The crew continued the takeoff over the illuminated RWSL system. The RWSL system was operating correctly and the THL portion of the system deactivated when the A321 reached a predetermined speed consistent with an aircraft continuing departure.
As the A321 was departing, the Airport Surface Detection Equipment Model X (ASDE-X) alerted and the air traffic controller responded by cancelling the takeoff clearance when the A321 was near takeoff speed. The A321 stopped on the runway about 500 feet from the airport vehicle.
Probable Cause: The air traffic controller's failure to ensure the runway surface area was clear of vehicles before clearing an aircraft for takeoff. Also causal was the flight crew's decision to initiate a takeoff while the Runway Status Lights (RWSL) Takeoff Hold Lights (THLs) were activated. Contributing to the incident was the lack of a standard procedure for vehicle operators to request runway clearances and resultant "hear back/read back" error between the vehicle operator and the air traffic controller.
Accident investigation:
 |
|
Sources:
NTSB OPS16IA004
Location
Revision history:
| Date/time | Contributor | Updates |
|---|---|---|
| 02-Jun-2023 13:57 | ASN Update Bot | Added |
Corrections or additions? ... Edit this accident description
The Aviation Safety Network is an exclusive service provided by:
Quick Links:
| ASN Home | Send Correction / Feedback |
| FSF Home | Disclaimer | Copyright |
| Contact Us | Privacy Policy |
| Press / Media |
CONNECT WITH US:
©2024 Flight Safety Foundation