A pilot created an airborne conflict with an inbound aircraft at fci when he turned after takeoff be...

Attributes
ACN	951300
Time
Date	201105
Local Time Of Day	1201-1800
Place
Locale Reference	FCI.Airport
State Reference	VA
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Make Model Name	Small Aircraft High Wing 1 Eng Fixed Gear
Operating Under FAR Part	Part 91
Flight Phase	Climb
Route In Use	VFR Route
Flight Plan	None
Aircraft 2
Flight Phase	Initial Approach
Person 1
Function	Single Pilot
Qualification	Flight Crew Commercial Flight Crew Flight Instructor
Experience	Flight Crew Last 90 Days 50 Flight Crew Total 7500 Flight Crew Type 5000
Events
Anomaly	Conflict Airborne Conflict Deviation - Procedural Published Material / Policy
Miss Distance	Horizontal 5000 Vertical 200

Narrative:

I was in the process of departing runway 15 at fci when I heard another aircraft being on an extended 5 mile left downwind. As I was climbing out; I turned onto the crosswind leg before reaching pattern altitude so that I could depart the pattern enroute before the arriving aircraft was close to the airport. It was my intent to avoid a possible conflict with the other aircraft; but instead created the conflict. As I switched over to potomac approach they advised of traffic at my 3 o'clock position. Even though I was below pattern altitude; the other aircraft was too close for comfort. I switched over to unicom and told the other pilot that I was sorry and that I didn't think I would ever be that close to his aircraft. No evasive action was taken due to the lack of seeing the aircraft too late when advised by potomac approach. In the future; I will abide by the traffic pattern procedures specified in the airmen information manual.

Original NASA ASRS Text

Title: A pilot created an airborne conflict with an inbound aircraft at FCI when he turned after takeoff before reaching the pattern altitude even though he was advised by PCT about the inbound aircraft.

Narrative: I was in the process of departing Runway 15 at FCI when I heard another aircraft being on an extended 5 mile left downwind. As I was climbing out; I turned onto the crosswind leg before reaching pattern altitude so that I could depart the pattern enroute before the arriving aircraft was close to the airport. It was my intent to avoid a possible conflict with the other aircraft; but instead created the conflict. As I switched over to Potomac Approach they advised of traffic at my 3 o'clock position. Even though I was below pattern altitude; the other aircraft was too close for comfort. I switched over to UNICOM and told the other pilot that I was sorry and that I didn't think I would ever be that close to his aircraft. No evasive action was taken due to the lack of seeing the aircraft too late when advised by Potomac Approach. In the future; I will abide by the traffic pattern procedures specified in the Airmen Information Manual.

Data retrieved from NASA's ASRS site as of April 2012 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.

A pilot created an airborne conflict with an inbound aircraft at fci when he turned after takeoff before reaching the pattern altitude even though he was advised by pct about the inbound aircraft.