37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 350821 |
Time | |
Date | 199610 |
Day | Sat |
Local Time Of Day | 1201 To 1800 |
Place | |
Locale Reference | airport : arb |
State Reference | MI |
Altitude | agl bound lower : 0 agl bound upper : 0 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | tower : eyw |
Operator | common carrier : air taxi |
Make Model Name | Any Unknown or Unlisted Aircraft Manufacturer |
Operating Under FAR Part | Part 91 |
Flight Phase | climbout : takeoff other |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : air taxi |
Function | flight crew : single pilot |
Qualification | pilot : atp |
Experience | flight time last 90 days : 44 flight time total : 2880 flight time type : 44 |
ASRS Report | 350821 |
Person 2 | |
Affiliation | government : faa |
Function | controller : local |
Qualification | controller : non radar |
Events | |
Anomaly | incursion : runway non adherence : far non adherence : clearance other anomaly other |
Independent Detector | other controllera |
Resolutory Action | controller : issued new clearance other |
Consequence | Other |
Supplementary | |
Primary Problem | Flight Crew Human Performance |
Air Traffic Incident | Pilot Deviation |
Narrative:
There was a lot of banner towing in progress and constant dropping of banners. Takeoff clearance was difficult to get. Then the controller asked whether I could make it and I replied yes. I then taxied to the runway in use and proceeded to begin the takeoff run. Then the controller alerted me about where I was going, then I realized something was wrong and immediately closed throttles. I was then asked to expedite clearing the runway which I did, but later taxied to holding point of runway 24. I believed it was caused by non standard phraseology at critical time. So I see that if you find yourself in a situation where unusual events prevent you from getting your takeoff clearance any communication between you and the tower have to be checked and clarified. Like in this case, the tower will try to get you off as soon as possible while juggling the other participants of the unusual event. Misunderstanding can be life. When the pressure mounts, slow down. Factors: unexpected delay to an IFR traffic. Aircraft was not visible from control tower where it was on holding point. A number of slower planes doing unusual thing at airport.
Original NASA ASRS Text
Title: PLT OF AN SMT TAXIED ONTO RWY AND STARTED TKOF WITHOUT CLRNC RESULTING IN TWR INTERVENTION TO ABORT THE TKOF AND CLR THE RWY AT ONCE.
Narrative: THERE WAS A LOT OF BANNER TOWING IN PROGRESS AND CONSTANT DROPPING OF BANNERS. TKOF CLRNC WAS DIFFICULT TO GET. THEN THE CTLR ASKED WHETHER I COULD MAKE IT AND I REPLIED YES. I THEN TAXIED TO THE RWY IN USE AND PROCEEDED TO BEGIN THE TKOF RUN. THEN THE CTLR ALERTED ME ABOUT WHERE I WAS GOING, THEN I REALIZED SOMETHING WAS WRONG AND IMMEDIATELY CLOSED THROTTLES. I WAS THEN ASKED TO EXPEDITE CLRING THE RWY WHICH I DID, BUT LATER TAXIED TO HOLDING POINT OF RWY 24. I BELIEVED IT WAS CAUSED BY NON STANDARD PHRASEOLOGY AT CRITICAL TIME. SO I SEE THAT IF YOU FIND YOURSELF IN A SIT WHERE UNUSUAL EVENTS PREVENT YOU FROM GETTING YOUR TKOF CLRNC ANY COM BTWN YOU AND THE TWR HAVE TO BE CHKED AND CLARIFIED. LIKE IN THIS CASE, THE TWR WILL TRY TO GET YOU OFF AS SOON AS POSSIBLE WHILE JUGGLING THE OTHER PARTICIPANTS OF THE UNUSUAL EVENT. MISUNDERSTANDING CAN BE LIFE. WHEN THE PRESSURE MOUNTS, SLOW DOWN. FACTORS: UNEXPECTED DELAY TO AN IFR TFC. ACFT WAS NOT VISIBLE FROM CTL TWR WHERE IT WAS ON HOLDING POINT. A NUMBER OF SLOWER PLANES DOING UNUSUAL THING AT ARPT.
Data retrieved from NASA's ASRS site as of July 2007 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.