Track deviation. Unstable approach procedure.

Attributes
ACN	144766
Time
Date	199005
Day	Fri
Local Time Of Day	1201 To 1800
Place
Locale Reference	airport : dtw
State Reference	MI
Altitude	msl bound lower : 1000 msl bound upper : 1500
Environment
Flight Conditions	IMC
Light	Daylight
Aircraft 1
Controlling Facilities	tracon : dtw tower : dtw
Operator	common carrier : air carrier
Make Model Name	Large Transport, Low Wing, 3 Turbojet Eng
Flight Phase	descent : approach
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : atp
Experience	flight time last 90 days : 180 flight time total : 5500 flight time type : 1800
ASRS Report	144766
Person 2
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : atp
Events
Anomaly	non adherence : published procedure non adherence : clearance other anomaly other other spatial deviation
Independent Detector	other controllera other flight crewa
Resolutory Action	flight crew : returned to intended course or assigned course
Consequence	Other
Supplementary
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

The captain was flying aircraft. A tornado watch had him worried and asked F/east to contact FSS to get details (descending into dtw). His radio interfered with communication on radio #2 which I was on with approach. During this confusion descent and approach clrncs had to be repeated a few times distracting my x-chk of captain's INS. Intercepting localizer captain went right through the localizer and I saw he had 66 degrees and not 33, as the approach calls for. I called out that and he put 33 in the window, corrected back and overshot again (approach asked if we needed vectors back for a new approach). He said no. I said, 'I do not like the look of this.' we had full localizer deflection and were above G/south. Captain said, 'let's see how it is at 1000'.' at 1000' he did manage to get back on localizer and kept descending to a successful landing. Captain had poor cockpit resource management and poor judgement. I should have said: 'go missed approach!!' F/east should have said that same, but was still doing checklist (late because of talking to FSS). It was first time I ever have seen an approach so messed up! I will never allow it to happen again!

Original NASA ASRS Text

Title: TRACK DEVIATION. UNSTABLE APCH PROC.

Narrative: THE CAPT WAS FLYING ACFT. A TORNADO WATCH HAD HIM WORRIED AND ASKED F/E TO CONTACT FSS TO GET DETAILS (DSNDING INTO DTW). HIS RADIO INTERFERED WITH COM ON RADIO #2 WHICH I WAS ON WITH APCH. DURING THIS CONFUSION DSNT AND APCH CLRNCS HAD TO BE REPEATED A FEW TIMES DISTRACTING MY X-CHK OF CAPT'S INS. INTERCEPTING LOC CAPT WENT RIGHT THROUGH THE LOC AND I SAW HE HAD 66 DEGS AND NOT 33, AS THE APCH CALLS FOR. I CALLED OUT THAT AND HE PUT 33 IN THE WINDOW, CORRECTED BACK AND OVERSHOT AGAIN (APCH ASKED IF WE NEEDED VECTORS BACK FOR A NEW APCH). HE SAID NO. I SAID, 'I DO NOT LIKE THE LOOK OF THIS.' WE HAD FULL LOC DEFLECTION AND WERE ABOVE G/S. CAPT SAID, 'LET'S SEE HOW IT IS AT 1000'.' AT 1000' HE DID MANAGE TO GET BACK ON LOC AND KEPT DSNDING TO A SUCCESSFUL LNDG. CAPT HAD POOR COCKPIT RESOURCE MGMNT AND POOR JUDGEMENT. I SHOULD HAVE SAID: 'GO MISSED APCH!!' F/E SHOULD HAVE SAID THAT SAME, BUT WAS STILL DOING CHKLIST (LATE BECAUSE OF TALKING TO FSS). IT WAS FIRST TIME I EVER HAVE SEEN AN APCH SO MESSED UP! I WILL NEVER ALLOW IT TO HAPPEN AGAIN!

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.