Narrative:

On departure from lna I taxied to runup area at hold line of taxiway at runway 3 at lna and completed preflight checks, runup procedure, etc, as normal. I had 1 aircraft depart ahead of me and waited for 1 plane to land. I then announced on unicom that I would taxi across runway 3 to the hold line on other side to allow a single engine cessna behind me to depart while I obtained an IFR clearance from palm beach approach while on the ground at lna on frequency 127.35. I then switched to approach while monitoring CTAF on second radio. I called approach and was offered an IFR clearance on ground which I accepted. I was then issued a short departure hold. During hold single engine cessna which had been behind me for takeoff took active runway. About this time I received a hold release. I waited for cessna to begin takeoff roll and taxied into position and held. After announcing my intentions on CTAF. While holding to allow adequate separation between the cessna and myself, I heard on unicom (unintelligible call sign) circling over approach end of runway 3.' based on this, I have reason to believe that I may have caused a conflict by taking the active runway. 15 seconds following this, I announced '(my call sign) departing runway 3' and began takeoff. I heard no further call from circling aircraft before contacting palm beach approach when airborne. I also point out that I heard no call from aircraft with conflict prior to the call announcing 'circling over approach end runway 3.' I also visually scanned the approach path prior to taxiing onto runway 3 and saw no aircraft at that time. It is possible that the aircraft was at an altitude of 1000 ft AGL which would have precluded easy spotting of aircraft. As was stated, I was unable to determine from radio xmissions if in fact any conflict occurred or if the circling was a maneuver to get into position for an approach, etc. If the event in question was a conflict, there appear to be a substantial number of causes.

Google
 

Original NASA ASRS Text

Title: PLTS HOLDING IN POS ON ACTIVE RWY AT NON TWRED ARPT MAY HAVE CAUSED CONFLICT IN TFC.

Narrative: ON DEP FROM LNA I TAXIED TO RUNUP AREA AT HOLD LINE OF TXWY AT RWY 3 AT LNA AND COMPLETED PREFLT CHKS, RUNUP PROC, ETC, AS NORMAL. I HAD 1 ACFT DEPART AHEAD OF ME AND WAITED FOR 1 PLANE TO LAND. I THEN ANNOUNCED ON UNICOM THAT I WOULD TAXI ACROSS RWY 3 TO THE HOLD LINE ON OTHER SIDE TO ALLOW A SINGLE ENG CESSNA BEHIND ME TO DEPART WHILE I OBTAINED AN IFR CLRNC FROM PALM BEACH APCH WHILE ON THE GND AT LNA ON FREQ 127.35. I THEN SWITCHED TO APCH WHILE MONITORING CTAF ON SECOND RADIO. I CALLED APCH AND WAS OFFERED AN IFR CLRNC ON GND WHICH I ACCEPTED. I WAS THEN ISSUED A SHORT DEP HOLD. DURING HOLD SINGLE ENG CESSNA WHICH HAD BEEN BEHIND ME FOR TKOF TOOK ACTIVE RWY. ABOUT THIS TIME I RECEIVED A HOLD RELEASE. I WAITED FOR CESSNA TO BEGIN TKOF ROLL AND TAXIED INTO POS AND HELD. AFTER ANNOUNCING MY INTENTIONS ON CTAF. WHILE HOLDING TO ALLOW ADEQUATE SEPARATION BTWN THE CESSNA AND MYSELF, I HEARD ON UNICOM (UNINTELLIGIBLE CALL SIGN) CIRCLING OVER APCH END OF RWY 3.' BASED ON THIS, I HAVE REASON TO BELIEVE THAT I MAY HAVE CAUSED A CONFLICT BY TAKING THE ACTIVE RWY. 15 SECONDS FOLLOWING THIS, I ANNOUNCED '(MY CALL SIGN) DEPARTING RWY 3' AND BEGAN TKOF. I HEARD NO FURTHER CALL FROM CIRCLING ACFT BEFORE CONTACTING PALM BEACH APCH WHEN AIRBORNE. I ALSO POINT OUT THAT I HEARD NO CALL FROM ACFT WITH CONFLICT PRIOR TO THE CALL ANNOUNCING 'CIRCLING OVER APCH END RWY 3.' I ALSO VISUALLY SCANNED THE APCH PATH PRIOR TO TAXIING ONTO RWY 3 AND SAW NO ACFT AT THAT TIME. IT IS POSSIBLE THAT THE ACFT WAS AT AN ALT OF 1000 FT AGL WHICH WOULD HAVE PRECLUDED EASY SPOTTING OF ACFT. AS WAS STATED, I WAS UNABLE TO DETERMINE FROM RADIO XMISSIONS IF IN FACT ANY CONFLICT OCCURRED OR IF THE CIRCLING WAS A MANEUVER TO GET INTO POS FOR AN APCH, ETC. IF THE EVENT IN QUESTION WAS A CONFLICT, THERE APPEAR TO BE A SUBSTANTIAL NUMBER OF CAUSES.

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.