Small transport makes go around as second aircraft does not takeoff promptly.

Attributes
ACN	306550
Time
Date	199506
Day	Fri
Local Time Of Day	1201 To 1800
Place
Locale Reference	airport : ane
State Reference	MN
Altitude	agl bound lower : 100 agl bound upper : 200
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Operator	general aviation : personal
Make Model Name	Cessna 310/T310C
Operating Under FAR Part	Part 91
Flight Phase	descent : approach
Flight Plan	None
Aircraft 2
Make Model Name	Skyhawk 172/Cutlass 172
Operating Under FAR Part	Part 91
Flight Phase	climbout : takeoff
Person 1
Affiliation	Other
Function	flight crew : single pilot
Qualification	pilot : atp pilot : cfi
Experience	flight time last 90 days : 180 flight time total : 13000 flight time type : 100
ASRS Report	306550
Person 2
Affiliation	Other
Function	flight crew : single pilot
Qualification	pilot : private
Events
Anomaly	conflict : nmac
Independent Detector	other flight crewa
Resolutory Action	flight crew : took evasive action other
Consequence	Other
Miss Distance	horizontal : 400 vertical : 200
Supplementary
Primary Problem	Flight Crew Human Performance

Narrative:

Approach to ane (anoka county, minneapolis area) from the northwest. Listened to CTAF 10 mi out, runway 8 in use, 2 aircraft in pattern. Made calls with position and intent to enter pattern on a left base for runway 8. Upon entry into left base there were no aircraft in pattern. However the 172 was back-taxiing for takeoff. I had all aircraft lights on (as usual). When I was turning rather short final the 172 announced it was going to takeoff runway 8 and proceeded to taxi into position on the runway and sat there and did nothing! At this point I'm on very short final and I call on the CTAF for the aircraft to get moving thinking they would get off. I continued the approach, however at approximately 150 ft AGL it became obvious they would not break ground in time for a safe landing so I went around. At that point they (the 172) lifted off. So as not to go right over her I promptly banked my aircraft to the right (keeping them in sight at all times) then back left to parallel their track. From that point we flew a normal pattern and returned for a landing. My point is pilots should be taught not to pull out onto a runway in front of landing traffic and then just situation there!

Original NASA ASRS Text

Title: SMT MAKES GAR AS SECOND ACFT DOES NOT TKOF PROMPTLY.

Narrative: APCH TO ANE (ANOKA COUNTY, MINNEAPOLIS AREA) FROM THE NW. LISTENED TO CTAF 10 MI OUT, RWY 8 IN USE, 2 ACFT IN PATTERN. MADE CALLS WITH POS AND INTENT TO ENTER PATTERN ON A L BASE FOR RWY 8. UPON ENTRY INTO L BASE THERE WERE NO ACFT IN PATTERN. HOWEVER THE 172 WAS BACK-TAXIING FOR TKOF. I HAD ALL ACFT LIGHTS ON (AS USUAL). WHEN I WAS TURNING RATHER SHORT FINAL THE 172 ANNOUNCED IT WAS GOING TO TKOF RWY 8 AND PROCEEDED TO TAXI INTO POS ON THE RWY AND SAT THERE AND DID NOTHING! AT THIS POINT I'M ON VERY SHORT FINAL AND I CALL ON THE CTAF FOR THE ACFT TO GET MOVING THINKING THEY WOULD GET OFF. I CONTINUED THE APCH, HOWEVER AT APPROX 150 FT AGL IT BECAME OBVIOUS THEY WOULD NOT BREAK GND IN TIME FOR A SAFE LNDG SO I WENT AROUND. AT THAT POINT THEY (THE 172) LIFTED OFF. SO AS NOT TO GO RIGHT OVER HER I PROMPTLY BANKED MY ACFT TO THE R (KEEPING THEM IN SIGHT AT ALL TIMES) THEN BACK L TO PARALLEL THEIR TRACK. FROM THAT POINT WE FLEW A NORMAL PATTERN AND RETURNED FOR A LNDG. MY POINT IS PLTS SHOULD BE TAUGHT NOT TO PULL OUT ONTO A RWY IN FRONT OF LNDG TFC AND THEN JUST SIT THERE!

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.