IFR C172 departure from lgb encounters conflict with aircraft entering wrong traffic pattern for run...

Attributes
ACN	640131
Time
Date	200412
Day	Wed
Local Time Of Day	1201 To 1800
Place
Locale Reference	airport : lgb.airport
State Reference	CA
Altitude	msl bound lower : 500 msl bound upper : 600
Environment
Flight Conditions	Mixed
Light	Daylight
Aircraft 1
Controlling Facilities	tower : lgb.tower
Operator	general aviation : personal
Make Model Name	Skyhawk 172/Cutlass 172
Operating Under FAR Part	Part 91
Flight Phase	climbout : takeoff
Route In Use	departure : on vectors
Flight Plan	IFR
Aircraft 2
Controlling Facilities	tower : lgb.tower
Make Model Name	Any Unknown or Unlisted Aircraft Manufacturer
Person 1
Affiliation	other
Function	flight crew : single pilot oversight : pic
Qualification	pilot : private
Experience	flight time last 90 days : 25 flight time total : 2900 flight time type : 2700
ASRS Report	640131
Person 2
Affiliation	other
Function	observation : observer
Events
Anomaly	conflict : nmac
Independent Detector	other flight crewa
Resolutory Action	flight crew : took precautionary avoidance action
Consequence	faa : reviewed incident with flight crew
Miss Distance	horizontal : 0 vertical : 200
Supplementary
Problem Areas	Flight Crew Human Performance ATC Human Performance
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

Having been cleared for takeoff, IFR, myself and a safety pilot were about 500 to 600 ft above the end of runway 30. I was concentrating on the instruments in preparation for going under the hood when my safety pilot remarked on glimpsing the sight of another plane about 200 to 300 ft directly above the top of the windscreen which quickly disappeared above our right wing. I then turned left to 200 degrees and continued to climb. Those are the clearance instructions and also would take us away from the other plane. The tower controller then came out with an apology of sorts and said the other plane should have been on left traffic for runway 25R. This did not make sense since only right traffic is allowed due to being close to runway 25L/7R. We switched to socal departure/approach for an ILS to runway 30 in lgb. When we landed, no one in the tower acknowledged nor commented on the incident. From the time we switched frequencys for takeoff clearance till the incident, tower never referred to another plane near our flight path.

Original NASA ASRS Text

Title: IFR C172 DEP FROM LGB ENCOUNTERS CONFLICT WITH ACFT ENTERING WRONG TFC PATTERN FOR RWY 25R.

Narrative: HAVING BEEN CLRED FOR TKOF, IFR, MYSELF AND A SAFETY PLT WERE ABOUT 500 TO 600 FT ABOVE THE END OF RWY 30. I WAS CONCENTRATING ON THE INSTS IN PREPARATION FOR GOING UNDER THE HOOD WHEN MY SAFETY PLT REMARKED ON GLIMPSING THE SIGHT OF ANOTHER PLANE ABOUT 200 TO 300 FT DIRECTLY ABOVE THE TOP OF THE WINDSCREEN WHICH QUICKLY DISAPPEARED ABOVE OUR R WING. I THEN TURNED L TO 200 DEGS AND CONTINUED TO CLB. THOSE ARE THE CLRNC INSTRUCTIONS AND ALSO WOULD TAKE US AWAY FROM THE OTHER PLANE. THE TWR CTLR THEN CAME OUT WITH AN APOLOGY OF SORTS AND SAID THE OTHER PLANE SHOULD HAVE BEEN ON L TFC FOR RWY 25R. THIS DID NOT MAKE SENSE SINCE ONLY R TFC IS ALLOWED DUE TO BEING CLOSE TO RWY 25L/7R. WE SWITCHED TO SOCAL DEP/APCH FOR AN ILS TO RWY 30 IN LGB. WHEN WE LANDED, NO ONE IN THE TWR ACKNOWLEDGED NOR COMMENTED ON THE INCIDENT. FROM THE TIME WE SWITCHED FREQS FOR TKOF CLRNC TILL THE INCIDENT, TWR NEVER REFERRED TO ANOTHER PLANE NEAR OUR FLT PATH.

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.

IFR C172 departure from lgb encounters conflict with aircraft entering wrong traffic pattern for runway 25R.