Runway incursion by a prospective renter pilot of a C172 at fll, fl

Attributes
ACN	539960
Time
Date	200203
Day	Tue
Local Time Of Day	1201 To 1800
Place
Locale Reference	airport : fxe.airport
State Reference	FL
Altitude	agl single value : 0
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Operator	general aviation : personal
Make Model Name	Skyhawk 172/Cutlass 172
Operating Under FAR Part	Part 91
Flight Phase	ground : taxi
Flight Plan	None
Person 1
Affiliation	other
Function	observation : passenger
Qualification	pilot : cfi
Experience	flight time last 90 days : 2.2 flight time total : 337 flight time type : 326
ASRS Report	539960
Person 2
Affiliation	other
Function	flight crew : single pilot
Events
Anomaly	aircraft equipment problem : less severe incursion : runway non adherence : far non adherence : published procedure other anomaly other
Independent Detector	other controllera
Resolutory Action	controller : issued new clearance controller : issued advisory flight crew : exited adverse environment flight crew : became reoriented
Consequence	faa : investigated faa : reviewed incident with flight crew
Supplementary
Problem Areas	Flight Crew Human Performance ATC Human Performance Aircraft Environmental Factor
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

The flight on mar/tue/02 was a chkout flight for a prospective rental customer, mr X, an FAA certified private pilot (asel). Mr X taxied to the active runway as per the instructions of the fxe ground control. At all times, he maintained positive radio contact with ground control. After the engine run-up, he taxied and held short of the active runway (runway 8). Mr X switched to the fxe tower frequency and announced his position as holding short of the active runway. No acknowledgement was heard. Additionally, I was unable to hear any of the messages from the tower to other aircraft, which prompted me to try adjusting my headset to ensure clarity of communication. Meanwhile, much to my surprise, I heard mr X telling the tower that he was cleared for takeoff, and initiating the turn onto the active runway! Almost immediately the tower came back to us, asking us to vacate the runway. They gave us a telephone number, with instructions to call them after the flight. The tower informed us that they had tried to get in touch with us and received no reply. Furthermore, they had not given the clearance to proceed onto the runway. After the flight, I took it upon myself to call the telephone number given. The gentleman who answered the call requested details, which included my address, telephone number, and pilot license number -- all of which I readily furnished. I was informed that the FSDO would get in touch with me. If I had any further questions or concerns, I was asked to call up their manager, ms Y, who would be available between XA00-XI00 hours the next day (mar/wed/02). The next day I called up ms Y and told her what had happened. She said that it was not me who was at fault. However, she added since they had already sent my details to the FSDO, there was little she could do, and I might hear from the FSDO in a few weeks time. She suggested that in case the FSDO contacted me, I should give mr X details (ie, pilot license number, address, and telephone number).

Original NASA ASRS Text

Title: RWY INCURSION BY A PROSPECTIVE RENTER PLT OF A C172 AT FLL, FL

Narrative: THE FLT ON MAR/TUE/02 WAS A CHKOUT FLT FOR A PROSPECTIVE RENTAL CUSTOMER, MR X, AN FAA CERTIFIED PVT PLT (ASEL). MR X TAXIED TO THE ACTIVE RWY AS PER THE INSTRUCTIONS OF THE FXE GND CTL. AT ALL TIMES, HE MAINTAINED POSITIVE RADIO CONTACT WITH GND CTL. AFTER THE ENG RUN-UP, HE TAXIED AND HELD SHORT OF THE ACTIVE RWY (RWY 8). MR X SWITCHED TO THE FXE TWR FREQ AND ANNOUNCED HIS POS AS HOLDING SHORT OF THE ACTIVE RWY. NO ACKNOWLEDGEMENT WAS HEARD. ADDITIONALLY, I WAS UNABLE TO HEAR ANY OF THE MESSAGES FROM THE TWR TO OTHER ACFT, WHICH PROMPTED ME TO TRY ADJUSTING MY HEADSET TO ENSURE CLARITY OF COM. MEANWHILE, MUCH TO MY SURPRISE, I HEARD MR X TELLING THE TWR THAT HE WAS CLRED FOR TKOF, AND INITIATING THE TURN ONTO THE ACTIVE RWY! ALMOST IMMEDIATELY THE TWR CAME BACK TO US, ASKING US TO VACATE THE RWY. THEY GAVE US A TELEPHONE NUMBER, WITH INSTRUCTIONS TO CALL THEM AFTER THE FLT. THE TWR INFORMED US THAT THEY HAD TRIED TO GET IN TOUCH WITH US AND RECEIVED NO REPLY. FURTHERMORE, THEY HAD NOT GIVEN THE CLRNC TO PROCEED ONTO THE RWY. AFTER THE FLT, I TOOK IT UPON MYSELF TO CALL THE TELEPHONE NUMBER GIVEN. THE GENTLEMAN WHO ANSWERED THE CALL REQUESTED DETAILS, WHICH INCLUDED MY ADDRESS, TELEPHONE NUMBER, AND PLT LICENSE NUMBER -- ALL OF WHICH I READILY FURNISHED. I WAS INFORMED THAT THE FSDO WOULD GET IN TOUCH WITH ME. IF I HAD ANY FURTHER QUESTIONS OR CONCERNS, I WAS ASKED TO CALL UP THEIR MGR, MS Y, WHO WOULD BE AVAILABLE BTWN XA00-XI00 HRS THE NEXT DAY (MAR/WED/02). THE NEXT DAY I CALLED UP MS Y AND TOLD HER WHAT HAD HAPPENED. SHE SAID THAT IT WAS NOT ME WHO WAS AT FAULT. HOWEVER, SHE ADDED SINCE THEY HAD ALREADY SENT MY DETAILS TO THE FSDO, THERE WAS LITTLE SHE COULD DO, AND I MIGHT HEAR FROM THE FSDO IN A FEW WKS TIME. SHE SUGGESTED THAT IN CASE THE FSDO CONTACTED ME, I SHOULD GIVE MR X DETAILS (IE, PLT LICENSE NUMBER, ADDRESS, AND TELEPHONE NUMBER).

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.