20200624008319I

N3225Q had just lifted off on runway 19 at kukf when the pilot became aware that another aircraft, N720TM was holding in position to take off on runway 01. The pilot of N3225Q aborted the takeoff and side stepped to the right. While attempting to land in the grass between the runway and taxiway, the left wing tip contacted the ground and the pilot lost control of the aircraft. The aircraft came to rest facing north in the grass, on its belly. No injuries were reported. Winds were calm. The PIC of N3225Q stated that he made proper radio calls on the CTAF 122.7 including taxi intentions and that he was departing runway 19. The pilot stated that the first radio traffic he heard was the abort call from the aircraft on runway 1. The PIC of N3225Q stated that the left main landing gear tire blew out during the landing attempt. Due to the aircraft being on its belly with the landing gear up following the incident, it could not be determined if the tire was in fact flat.

The pilot of N720TM provided the following statement:

The airport has one runway, 1-19, 6200' long with one parallel taxiway (a) and five perpendicular taxiways all unmarked on the airport diagrams. Parts of taxiway a and the three southern perpendicular taxiways were close due to construction. Only the two north perpendicular taxiways were open.

About 1115, we called on UNICOM to take the runway for a back taxi in order to takeoff into the favorable reported winds, 010/05. As we back taxied southward on runway 19 for a runway 1 departure, the co-pilot was making

Radio calls to atlanta center in order to get our take off clearance. When we were about half the way back-taxiing on the runway, atlanta center asked how close we were until we were

Ready for takeoff. It was then our comms with atlanta center ceased and were unreachable.

We kept taxiing and made it to the end where I did a 180* turn to position the aircraft for a takeoff to the north on runway 01.

After a few attempts to get to atlanta center we gave up and switched to raleigh radio. The copilot was successful contacting them. They informed us we had to wait while they got in touch with atlanta center. Raleigh radio informed us that atlanta center was on a sector change and their normal contact has changed so we would have to wait until they could figure out who is coming on, in order to get our release. Stand by.

There is a general note on the airport page, jeppesen kukf page 10-9A that states: "no line of sight between runway ends" as we were standing by on the departure end of runway 1, a baron aircraft called, his first call

On UNICOM frequency, that he was taking runway 19 for takeoff. Again, this was his first call and we could not see the opposite side of the runway, nor could he see us. We had been sitting there for at least five minutes at this point. I made a call on UNICOM: there is a Hawker sitting on the runway on the departure end of rwy 1, do not depart. The baron made a second call a few seconds later that he was taking off on runway 19. I immediately announced on

UNICOM to the baron, aircraft taking off of runway 19, you have an aircraft at your departure end, "abort, abort, abort". I rationalized there was plenty of time to stop on the runway because he couldn't have been airborne yet. What seemed like a second or two later that the baron appeared over the peak of the horizon and it was in fact, airborne. It then started to waffle, left and right wing rocking back and forth, and the aircraft changed heading about 10-20 degrees to his right. It wasn't clear if the airborne aircraft was going to continue its airborne commitment having apparently passed V1 speed. However, apparently with the gear up, with one wing dipped, the baron impacted the ground, slid and spun around and stopped in the grass. The impact was observed from about 3000' away, mid field, while we were still on the departure end of runway 1.

.....Continued in block 43.