Air carrier X received GPWS on visual approach because controller assigned speed restr.

Attributes
ACN	268782
Time
Date	199404
Day	Sat
Local Time Of Day	1801 To 2400
Place
Locale Reference	atc facility : rno
State Reference	NV
Altitude	agl bound lower : 3000 agl bound upper : 3000
Environment
Flight Conditions	VMC
Light	Night
Aircraft 1
Controlling Facilities	tracon : rno
Operator	common carrier : air carrier
Make Model Name	MD-80 Series (DC-9-80) Undifferentiated or Other Model
Operating Under FAR Part	Part 121
Navigation In Use	Other
Flight Phase	descent : approach
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : atp
Experience	flight time last 90 days : 50 flight time total : 8400 flight time type : 1200
ASRS Report	268782
Person 2
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : commercial pilot : instrument
Events
Anomaly	other anomaly other spatial deviation
Independent Detector	aircraft equipment other aircraft equipment : unspecified
Resolutory Action	none taken : anomaly accepted
Consequence	Other
Supplementary
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	other

Narrative:

Air carrier X straight-in night visual approach, first officer flying. We flew a particularly fast descent and approach. At 12 DME, the approach controller asked for our speed. I responded, `220 and slowing'. He asked `give me that speed to an 8 mi final' I replied, `unable'. He then tried to negotiate several other combinations of speed and distance. While we were talking the first officer advanced the throttles and dove a little in an attempt to comply. As a result, the GPWS `terrain' mode activated. This mode doesn't cancel until the airplane imitates a climb, so we were forced to listen to the word terrain for most of the rest of the approach. If we got a handoff to tower, we couldn't hear it for the GPWS. I changed to tower and received a landing clearance, but in the process of helping the first officer to get the airplane stabilized, I neglected to complete the landing checklist. Fortunately, everything was completed anyway. Observation: the first officer should not have changed his plan for speeds, profile, and confign that late in the game. He was going to have a little trouble getting slowed down as it was, and attempting to help ATC almost made the approach unworkable.

Original NASA ASRS Text

Title: ACR X RECEIVED GPWS ON VISUAL APCH BECAUSE CTLR ASSIGNED SPD RESTR.

Narrative: ACR X STRAIGHT-IN NIGHT VISUAL APCH, FO FLYING. WE FLEW A PARTICULARLY FAST DSCNT AND APCH. AT 12 DME, THE APCH CTLR ASKED FOR OUR SPD. I RESPONDED, `220 AND SLOWING'. HE ASKED `GIVE ME THAT SPD TO AN 8 MI FINAL' I REPLIED, `UNABLE'. HE THEN TRIED TO NEGOTIATE SEVERAL OTHER COMBINATIONS OF SPD AND DISTANCE. WHILE WE WERE TALKING THE FO ADVANCED THE THROTTLES AND DOVE A LITTLE IN AN ATTEMPT TO COMPLY. AS A RESULT, THE GPWS `TERRAIN' MODE ACTIVATED. THIS MODE DOESN'T CANCEL UNTIL THE AIRPLANE IMITATES A CLB, SO WE WERE FORCED TO LISTEN TO THE WORD TERRAIN FOR MOST OF THE REST OF THE APCH. IF WE GOT A HDOF TO TWR, WE COULDN'T HEAR IT FOR THE GPWS. I CHANGED TO TWR AND RECEIVED A LNDG CLRNC, BUT IN THE PROCESS OF HELPING THE FO TO GET THE AIRPLANE STABILIZED, I NEGLECTED TO COMPLETE THE LNDG CHKLIST. FORTUNATELY, EVERYTHING WAS COMPLETED ANYWAY. OBSERVATION: THE FO SHOULD NOT HAVE CHANGED HIS PLAN FOR SPDS, PROFILE, AND CONFIGN THAT LATE IN THE GAME. HE WAS GOING TO HAVE A LITTLE TROUBLE GETTING SLOWED DOWN AS IT WAS, AND ATTEMPTING TO HELP ATC ALMOST MADE THE APCH UNWORKABLE.

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.