Narrative:

Upon finishing our takeoff checklist for the BE76 at the run-up area by runway 26 at ftg, we taxied to the hold short line of runway 26 waiting for a C172 to land and announced that we were holding short of runway 26 for takeoff. The winds were reporting 190 degrees at 7 KTS. After the C172 touched down, we taxied into position and held on runway 26 waiting for the C172 to clear the runway and again announced our intentions to take runway 26 for departure. Upon starting our takeoff roll, we heard a garbled transmission about runway 8. We immediately queried the CTAF/unicom if there was traffic on runway 8. After no response and no visual sign of an aircraft, we again called CTAF/unicom and asked if there was an aircraft calling about runway 8. Again no response was given. Around 65 KIAS (vr is 71), we made a visual sighting of the twin piper rolling on runway 8. Immediately we began a rejected takeoff and announced, 'rejecting, rejecting runway 26,' on the CTAF/unicom. During the rejection, the right main tire on our BE76 blew out. We maintained directional control and pulled safely to the right side of runway 26. The piper stopped and pulled off on a taxiway. We called CTAF/unicom 3 times to inform them we were disabled on runway 26 before we received a reply. Contributing factors include the failure of the piper to communicate clearly and utilizing the wrong runway per winds, traffic, designated calm-variable wind runway of runway 27. Also, the piper's landing light was off, making him difficult to see at the non-controled airport in a see and be seen, high density traffic environment. Supplemental information from acn 612168: the piper stopped approximately 250 ft from our position where he was disabled.

Related reports:

Google
 

Original NASA ASRS Text

Title: BE76 ABORTED TKOF ON RWY 26 AT FTG AFTER OBSERVING TWIN PIPER ROLLING OPPOSITE DIRECTION ON RWY 8.

Narrative: UPON FINISHING OUR TKOF CHKLIST FOR THE BE76 AT THE RUN-UP AREA BY RWY 26 AT FTG, WE TAXIED TO THE HOLD SHORT LINE OF RWY 26 WAITING FOR A C172 TO LAND AND ANNOUNCED THAT WE WERE HOLDING SHORT OF RWY 26 FOR TKOF. THE WINDS WERE RPTING 190 DEGS AT 7 KTS. AFTER THE C172 TOUCHED DOWN, WE TAXIED INTO POS AND HELD ON RWY 26 WAITING FOR THE C172 TO CLR THE RWY AND AGAIN ANNOUNCED OUR INTENTIONS TO TAKE RWY 26 FOR DEP. UPON STARTING OUR TKOF ROLL, WE HEARD A GARBLED XMISSION ABOUT RWY 8. WE IMMEDIATELY QUERIED THE CTAF/UNICOM IF THERE WAS TFC ON RWY 8. AFTER NO RESPONSE AND NO VISUAL SIGN OF AN ACFT, WE AGAIN CALLED CTAF/UNICOM AND ASKED IF THERE WAS AN ACFT CALLING ABOUT RWY 8. AGAIN NO RESPONSE WAS GIVEN. AROUND 65 KIAS (VR IS 71), WE MADE A VISUAL SIGHTING OF THE TWIN PIPER ROLLING ON RWY 8. IMMEDIATELY WE BEGAN A REJECTED TKOF AND ANNOUNCED, 'REJECTING, REJECTING RWY 26,' ON THE CTAF/UNICOM. DURING THE REJECTION, THE R MAIN TIRE ON OUR BE76 BLEW OUT. WE MAINTAINED DIRECTIONAL CTL AND PULLED SAFELY TO THE R SIDE OF RWY 26. THE PIPER STOPPED AND PULLED OFF ON A TXWY. WE CALLED CTAF/UNICOM 3 TIMES TO INFORM THEM WE WERE DISABLED ON RWY 26 BEFORE WE RECEIVED A REPLY. CONTRIBUTING FACTORS INCLUDE THE FAILURE OF THE PIPER TO COMMUNICATE CLRLY AND UTILIZING THE WRONG RWY PER WINDS, TFC, DESIGNATED CALM-VARIABLE WIND RWY OF RWY 27. ALSO, THE PIPER'S LNDG LIGHT WAS OFF, MAKING HIM DIFFICULT TO SEE AT THE NON-CTLED ARPT IN A SEE AND BE SEEN, HIGH DENSITY TFC ENVIRONMENT. SUPPLEMENTAL INFO FROM ACN 612168: THE PIPER STOPPED APPROX 250 FT FROM OUR POS WHERE HE WAS DISABLED.

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.