Ground conflict during an uncoordinated runway entry at a non tower airport unicom.

Attributes
ACN	311911
Time
Date	199507
Day	Fri
Local Time Of Day	0601 To 1200
Place
Locale Reference	airport : tnt
State Reference	FL
Altitude	agl bound lower : 0 agl bound upper : 0
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Operator	general aviation : personal
Make Model Name	Baron 55/Cochise
Operating Under FAR Part	Part 91
Flight Phase	ground other : taxi
Flight Plan	VFR
Aircraft 2
Make Model Name	Any Unknown or Unlisted Aircraft Manufacturer
Operating Under FAR Part	other : unknown
Flight Phase	descent : approach landing : go around
Flight Plan	VFR
Person 1
Affiliation	Other
Function	flight crew : single pilot instruction : trainee
Qualification	pilot : instrument pilot : private
Experience	flight time last 90 days : 50 flight time total : 200 flight time type : 50
ASRS Report	311911
Person 2
Affiliation	Other
Function	instruction : instructor oversight : pic
Qualification	pilot : instrument pilot : commercial pilot : cfi
Events
Anomaly	conflict : ground critical non adherence : published procedure other anomaly other
Independent Detector	other flight crewa other other : unspecified
Resolutory Action	flight crew : took evasive action flight crew : exited adverse environment
Consequence	Other
Miss Distance	horizontal : 500 vertical : 200
Supplementary
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

I was flying a beech baron 55 with an FAA approved examiner on board as part of my instrument rating test. I was instructed to fly an ILS runway 9 approach at dade/collier airport. Through unicom the examiner advised traffic about our position. After landing I taxied back to runway 9 on the taxiway. During taxi I informed traffic via unicom that I was taxiing back to runway 9 for takeoff. Before leaving the taxiway, the examiner again informed traffic via unicom that 'baron xx will takeoff of runway 9 at dade/collier.' no other information was given through unicom. While turning onto the runway the examiner suddenly ordered me to swing the aircraft around to the left. At this moment I also could see a multi-engine plane in the final phase of the approach. I gave full throttle on the right engine and cleared the runway. The approaching aircraft made a go around. I still do not understand why nobody in my aircraft could see the approaching aircraft. This possible dangerous situation could have been avoided by giving position reports via unicom by the approaching aircraft as well as more careful scanning of the approach path by myself.

Original NASA ASRS Text

Title: GND CONFLICT DURING AN UNCOORDINATED RWY ENTRY AT A NON TWR ARPT UNICOM.

Narrative: I WAS FLYING A BEECH BARON 55 WITH AN FAA APPROVED EXAMINER ON BOARD AS PART OF MY INST RATING TEST. I WAS INSTRUCTED TO FLY AN ILS RWY 9 APCH AT DADE/COLLIER ARPT. THROUGH UNICOM THE EXAMINER ADVISED TFC ABOUT OUR POS. AFTER LNDG I TAXIED BACK TO RWY 9 ON THE TXWY. DURING TAXI I INFORMED TFC VIA UNICOM THAT I WAS TAXIING BACK TO RWY 9 FOR TKOF. BEFORE LEAVING THE TXWY, THE EXAMINER AGAIN INFORMED TFC VIA UNICOM THAT 'BARON XX WILL TKOF OF RWY 9 AT DADE/COLLIER.' NO OTHER INFO WAS GIVEN THROUGH UNICOM. WHILE TURNING ONTO THE RWY THE EXAMINER SUDDENLY ORDERED ME TO SWING THE ACFT AROUND TO THE L. AT THIS MOMENT I ALSO COULD SEE A MULTI-ENG PLANE IN THE FINAL PHASE OF THE APCH. I GAVE FULL THROTTLE ON THE R ENG AND CLRED THE RWY. THE APCHING ACFT MADE A GAR. I STILL DO NOT UNDERSTAND WHY NOBODY IN MY ACFT COULD SEE THE APCHING ACFT. THIS POSSIBLE DANGEROUS SIT COULD HAVE BEEN AVOIDED BY GIVING POS RPTS VIA UNICOM BY THE APCHING ACFT AS WELL AS MORE CAREFUL SCANNING OF THE APCH PATH BY MYSELF.

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.