UNAUTH TKOF ON OCCUPIED RWY.

Date: 1994-05 · Aircraft: Any Unknown or Unlisted Aircraft Manufacturer

Anomalies: conflict-ground-conflict|critical|deviation-discrepancy-procedural-far|deviation-discrepancy-procedural-other-unknown|ground-incursion-runway

Synopsis

UNAUTH TKOF ON OCCUPIED RWY.

Narrative

AFTER RUNUP AND RECEIVING IFR CLRNC AT RUNUP AREA OFF RWY 12 AT VISALIA MUNI; I SWITCHED BACK TO CTAF 123.05 AND ANNOUNCED MY DEP ON RWY 12 VISIBILITY. TAXIED ON TO THE RWY AND DEPARTED. NO ACFT WERE HEARD ON THE CTAF OR SEEN ON THE RWY. RWY 12 WAS USED BECAUSE AWOS WINDS WERE 6-7 KTS AND MY RTE DIRECTION WAS S ON V-23 TO EHF. APPROX 5-6 MINS AFTER TKOF I HEARD AN ACFT INQUIRING TO ATC IF THEY HAD TALKED TO A CHEROKEE THAT HAD DEPARTED VISIBILITY 5 MIN BEFORE BECAUSE THE CHEROKEE COULD HAVE CAUSED A SERIOUS INCIDENT. ATC STATED NO CHEROKEE BUT HAD TALKED TO A GRUMMAN ABOUT THAT TIME. MY PAX AND I BOTH STATED WE HAD NEITHER HEARD AN ACFT ON THE CTAF BEFORE OR AFTER MY DEP ANNOUNCEMENT; NOR DID WE SEE ANOTHER ACFT ON THE RWY OR AFTER TKOF. WE WONDERED WHAT COULD HAVE HAPPENED. LATER THAT DAY; UPON RETURNING TO OUR HOME; THERE WAS A MESSAGE ON OUR ANSWERING MACHINE TO CALL THE FAA IN FRESNO. UPON CONTACTING HIM; HE TOLD ME A MAIL SVC CARAVAN WAS ON THE END OF RWY 30 AND THAT HE HAD TRIED TO CONTACT THE OTHER ACFT AND THAT IT HAD FLOWN OVER HIM ON TKOF. I REPEATED THE DETAILS FROM MY VIEWPOINT AS DETAILED ABOVE. THIS SIT COULD BE AVOIDED IF THE TKOF RWY USED WAS ALWAYS THE PREVAILING WIND REGARDLESS OF WIND LEVEL OR DESIRED DIRECTION OF FLT.

Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.