37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1512332 |
Time | |
Date | 201801 |
Local Time Of Day | 1201-1800 |
Place | |
Locale Reference | ZZZ.Airport |
State Reference | US |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Make Model Name | Citation Excel (C560XL) |
Operating Under FAR Part | Part 135 |
Flight Phase | Takeoff |
Flight Plan | IFR |
Person 1 | |
Function | Pilot Not Flying Captain |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Events | |
Anomaly | ATC Issue All Types Deviation - Procedural Published Material / Policy |
Narrative:
We were delayed out of ZZZ due to customs and border protection (cbp) requiring us to deplane all crew and passengers on our fuel stop to ZZZZ. We all had to drive to cbp for approval and stamp our outbound gendec. By the time we began our taxi out we were already significantly delayed. Due to taxiway closures we had to back taxi most of runway xx. Upon reaching the end of the runway tower cleared us for takeoff. As soon as we began adding power and had started our takeoff roll; tower stated that our takeoff clearance was cancelled. Just as we started to reduce power and add brakes tower called us back and told us to disregard. He informed us that he had received a phone call from cbp and thought there might be an issue with our departure release. He said that we were still cleared for takeoff. Although we had used very little runway; I requested that we turn around and back taxi the runway a second time for full and verifiable length. We departed as normal and tower apologized for his mistake on the handoff to departure control. Once we arrived I verified the rejected takeoff policy in the fom and realized my mistake. Although takeoff power had not been applied; we were still considered a rejected takeoff due to the initiation of the takeoff roll per the fom definition. To comply with company policy we should have exited the runway and called flight control prior to our departure.
Original NASA ASRS Text
Title: Cessna Citation Captain reported a Tower directed rejected takeoff; due to a Customs/Border Patrol issue. The situation was quickly resolved and the pilot taxied back to the takeoff position; however he failed to notify his company of the aborted takeoff event.
Narrative: We were delayed out of ZZZ due to Customs and Border Protection (CBP) requiring us to deplane all crew and passengers on our fuel stop to ZZZZ. We all had to drive to CBP for approval and stamp our outbound GENDEC. By the time we began our taxi out we were already significantly delayed. Due to taxiway closures we had to back taxi most of Runway XX. Upon reaching the end of the runway tower cleared us for takeoff. As soon as we began adding power and had started our takeoff roll; tower stated that our takeoff clearance was cancelled. Just as we started to reduce power and add brakes tower called us back and told us to disregard. He informed us that he had received a phone call from CBP and thought there might be an issue with our departure release. He said that we were still cleared for takeoff. Although we had used very little runway; I requested that we turn around and back taxi the runway a second time for full and verifiable length. We departed as normal and tower apologized for his mistake on the handoff to departure control. Once we arrived I verified the rejected takeoff policy in the FOM and realized my mistake. Although takeoff power had not been applied; we were still considered a rejected takeoff due to the initiation of the takeoff roll per the FOM definition. To comply with company policy we should have exited the runway and called flight control prior to our departure.
Data retrieved from NASA's ASRS site 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.