An instructor is very contrite about 2 incidents in 2 days of coming close to another aircraft.

Attributes
ACN	266749
Time
Date	199403
Day	Wed
Local Time Of Day	1201 To 1800
Place
Locale Reference	airport : fty
State Reference	GA
Altitude	msl bound lower : 3000 msl bound upper : 3000
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	tracon : atl
Operator	general aviation : instructional
Make Model Name	Any Unknown or Unlisted Aircraft Manufacturer
Operating Under FAR Part	Part 91
Flight Phase	cruise other descent : approach
Route In Use	enroute airway : fty
Flight Plan	None
Aircraft 2
Make Model Name	Beechcraft Twin Turboprop Jet Undifferentiated or Other Model
Operating Under FAR Part	other : unknown
Flight Phase	climbout : intermediate altitude
Person 1
Affiliation	Other
Function	flight crew : single pilot instruction : instructor
Qualification	pilot : instrument pilot : cfi pilot : commercial
Experience	flight time last 90 days : 120 flight time total : 1200 flight time type : 180
ASRS Report	266749
Person 2
Affiliation	Other
Function	flight crew : single pilot instruction : instructor
Qualification	pilot : cfi pilot : commercial pilot : instrument
Experience	flight time last 90 days : 120 flight time total : 1200 flight time type : 180
ASRS Report	266740
Events
Anomaly	conflict : airborne less severe non adherence : clearance non adherence : far other anomaly other
Independent Detector	other flight crewa
Resolutory Action	flight crew : took evasive action
Consequence	Other
Miss Distance	horizontal : 2500 vertical : 0
Supplementary
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

The problem arose when I contacted atl approach for an ILS runway 8 into fty. Fty was using runway 26 and while we usually get the approach anyhow, atl denied the approach this day. I decided to shoot the approach on my own and contact the tower for advisories on departing traffic. Before I called the tower, however, I saw a king air level at my altitude and approaching from my 11 O'clock. I executed a steep (50 degrees or so) turn to the right to avoid the traffic. I rolled out on the king air's heading and watched him pass us at a safe distance. I don't know if the king air saw us and can only guess whether he was notified by departure of our position. This was the second time in a week I have found myself on course toward another aircraft. Things I could do different in the future is just hold someplace until there is room between departures for us to shoot an opposite direction approach and use approach for TA's even if I am shooting the approach on my own navigation.

Original NASA ASRS Text

Title: AN INSTRUCTOR IS VERY CONTRITE ABOUT 2 INCIDENTS IN 2 DAYS OF COMING CLOSE TO ANOTHER ACFT.

Narrative: THE PROB AROSE WHEN I CONTACTED ATL APCH FOR AN ILS RWY 8 INTO FTY. FTY WAS USING RWY 26 AND WHILE WE USUALLY GET THE APCH ANYHOW, ATL DENIED THE APCH THIS DAY. I DECIDED TO SHOOT THE APCH ON MY OWN AND CONTACT THE TWR FOR ADVISORIES ON DEPARTING TFC. BEFORE I CALLED THE TWR, HOWEVER, I SAW A KING AIR LEVEL AT MY ALT AND APCHING FROM MY 11 O'CLOCK. I EXECUTED A STEEP (50 DEGS OR SO) TURN TO THE R TO AVOID THE TFC. I ROLLED OUT ON THE KING AIR'S HDG AND WATCHED HIM PASS US AT A SAFE DISTANCE. I DON'T KNOW IF THE KING AIR SAW US AND CAN ONLY GUESS WHETHER HE WAS NOTIFIED BY DEP OF OUR POS. THIS WAS THE SECOND TIME IN A WK I HAVE FOUND MYSELF ON COURSE TOWARD ANOTHER ACFT. THINGS I COULD DO DIFFERENT IN THE FUTURE IS JUST HOLD SOMEPLACE UNTIL THERE IS ROOM BTWN DEPS FOR US TO SHOOT AN OPPOSITE DIRECTION APCH AND USE APCH FOR TA'S EVEN IF I AM SHOOTING THE APCH ON MY OWN NAV.

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.