Wrong altitude approach creates a potential conflict for the flight crew of a BE400 southwest of jax...

Attributes
ACN	537550
Time
Date	200202
Day	Fri
Local Time Of Day	0601 To 1200
Place
Locale Reference	airport : jax.airport
State Reference	FL
Altitude	msl single value : 3000
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	tracon : jax.tracon
Operator	general aviation : corporate
Make Model Name	Beechjet 400
Operating Under FAR Part	Part 91
Navigation In Use	other
Flight Phase	descent : approach
Route In Use	approach : visual arrival : on vectors
Flight Plan	IFR
Aircraft 2
Controlling Facilities	tracon : jax.tracon
Flight Phase	cruise : level
Person 1
Affiliation	company : corporate
Function	flight crew : captain oversight : pic
Qualification	pilot : atp
Experience	flight time last 90 days : 50 flight time total : 8700 flight time type : 700
ASRS Report	537550
Person 2
Affiliation	company : corporate
Function	flight crew : first officer
Events
Anomaly	non adherence : far non adherence : required legal separation non adherence : clearance other anomaly other other spatial deviation
Independent Detector	atc equipment other atc equipment : radar other controllera
Resolutory Action	controller : separated traffic controller : issued new clearance controller : issued advisory flight crew : became reoriented flight crew : returned to intended or assigned course
Consequence	faa : reviewed incident with flight crew
Supplementary
Problem Areas	ATC Human Performance Airport Flight Crew Human Performance
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

Flight originated from sgj to jax. Initial clearance was to climb to 2000 ft, heading 310 degrees, which was complied with. Final altitude cleared to was 5000 ft. When I had what I thought was jax in sight, I told the approach controller 'airport in sight.' the airport that I was looking at, which from my position had the correct runway alignment, was not jax, but white houser field. We were given a descent to 3000 ft and informed of traffic below us at 2000 ft. We were cleared for a visual approach to runway 7 at jax. We then started a left turn and descended from 3000 ft to 2800 ft with traffic below in visual contact. I was asked by the controller what airport I had in sight. Before answering, the controller came back with a vector of 020 degrees and altitude of 2000 ft, followed by additional vectors to a visual approach to runway 7 at jax. Upon landing and contacting ground, I was asked to call the controller supervisor. He said lost separation had occurred and thought it would be considered a pilot deviation. I told him I was very sorry the situation had happened. Also, I told him of the wrong airport in sight initially, verifying jax airport, shortly after visual approach clearance received, visual approach clearance to runway 7 and previously called traffic in sight with visual separation maintained with no indication from controller of other aircraft climbing. Corrective action I should take in the future would be to never call airport in sight until absolutely verified with all means available.

Original NASA ASRS Text

Title: WRONG ALT APCH CREATES A POTENTIAL CONFLICT FOR THE FLC OF A BE400 SW OF JAX, FL.

Narrative: FLT ORIGINATED FROM SGJ TO JAX. INITIAL CLRNC WAS TO CLB TO 2000 FT, HDG 310 DEGS, WHICH WAS COMPLIED WITH. FINAL ALT CLRED TO WAS 5000 FT. WHEN I HAD WHAT I THOUGHT WAS JAX IN SIGHT, I TOLD THE APCH CTLR 'ARPT IN SIGHT.' THE ARPT THAT I WAS LOOKING AT, WHICH FROM MY POS HAD THE CORRECT RWY ALIGNMENT, WAS NOT JAX, BUT WHITE HOUSER FIELD. WE WERE GIVEN A DSCNT TO 3000 FT AND INFORMED OF TFC BELOW US AT 2000 FT. WE WERE CLRED FOR A VISUAL APCH TO RWY 7 AT JAX. WE THEN STARTED A L TURN AND DSNDED FROM 3000 FT TO 2800 FT WITH TFC BELOW IN VISUAL CONTACT. I WAS ASKED BY THE CTLR WHAT ARPT I HAD IN SIGHT. BEFORE ANSWERING, THE CTLR CAME BACK WITH A VECTOR OF 020 DEGS AND ALT OF 2000 FT, FOLLOWED BY ADDITIONAL VECTORS TO A VISUAL APCH TO RWY 7 AT JAX. UPON LNDG AND CONTACTING GND, I WAS ASKED TO CALL THE CTLR SUPVR. HE SAID LOST SEPARATION HAD OCCURRED AND THOUGHT IT WOULD BE CONSIDERED A PLTDEV. I TOLD HIM I WAS VERY SORRY THE SIT HAD HAPPENED. ALSO, I TOLD HIM OF THE WRONG ARPT IN SIGHT INITIALLY, VERIFYING JAX ARPT, SHORTLY AFTER VISUAL APCH CLRNC RECEIVED, VISUAL APCH CLRNC TO RWY 7 AND PREVIOUSLY CALLED TFC IN SIGHT WITH VISUAL SEPARATION MAINTAINED WITH NO INDICATION FROM CTLR OF OTHER ACFT CLBING. CORRECTIVE ACTION I SHOULD TAKE IN THE FUTURE WOULD BE TO NEVER CALL ARPT IN SIGHT UNTIL ABSOLUTELY VERIFIED WITH ALL MEANS AVAILABLE.

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.

Wrong altitude approach creates a potential conflict for the flight crew of a BE400 southwest of jax, fl.