 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
B767-300 on approach to runway 35C was high and fast near the OM. Unable to get stabilized and had to go around. Approach control has a habit of keeping aircraft high and fast.
| Attributes | |
| ACN | 361327 |
| Time | |
| Date | 199702 |
| Day | Sat |
| Local Time Of Day | 1801 To 2400 |
| Place | |
| Locale Reference | airport : dfw |
| State Reference | TX |
| Altitude | agl bound lower : 1000 agl bound upper : 1000 |
| Environment | |
| Flight Conditions | VMC |
| Light | Dusk |
| Aircraft 1 | |
| Controlling Facilities | tracon : dfw |
| Operator | common carrier : air carrier |
| Make Model Name | B767-300 and 300 ER |
| Operating Under FAR Part | Part 121 |
| Navigation In Use | Other Other |
| Flight Phase | descent : approach landing : go around |
| Route In Use | approach : visual |
| Flight Plan | IFR |
| Person 1 | |
| Affiliation | company : air carrier |
| Function | flight crew : captain oversight : pic |
| Qualification | pilot : atp |
| Experience | flight time last 90 days : 80 flight time total : 13000 |
| ASRS Report | 361327 |
| Person 2 | |
| Affiliation | company : air carrier |
| Function | flight crew : first officer |
| Qualification | pilot : commercial pilot : instrument |
| Events | |
| Anomaly | other anomaly other |
| Independent Detector | other flight crewa |
| Resolutory Action | controller : issued new clearance other |
| Consequence | Other |
| Supplementary | |
| Primary Problem | ATC Human Performance |
| Air Traffic Incident | other |
| Situations | |
| ATC Facility | procedure or policy : unspecified |
Narrative:
We had to miss the approach to runway 35C at dfw due to an unstablized approach. We were asked to maintain 4000 ft and 180 KTS until final approach course. That put us just outside the marker 1700 ft high and too fast for more than 20 degree flaps. Try as we might couldn't get stabilized by 1000 ft, in fact we wouldn't have been stabilized at 500 ft either. The controller's requests put us beyond the capabilities of our aircraft to safely fly the approach and landing. We went around and the next approach and landing were normal. Dfw is notorious for last min runway changes, which we got, but were prepared for because they always do it. I know ATC was trying to help us out by giving us a runway closer to our gate, but with the constraints of altitude and airspeed put us beyond the capabilities of our aircraft. I'm not sure they understand some of our limitations and our need for a stabilized approach. Our missed approach cost us time, fuel, and passenger fear or discomfort.
Original NASA ASRS Text
Title: B767-300 ON APCH TO RWY 35C WAS HIGH AND FAST NEAR THE OM. UNABLE TO GET STABILIZED AND HAD TO GAR. APCH CTL HAS A HABIT OF KEEPING ACFT HIGH AND FAST.
Narrative: WE HAD TO MISS THE APCH TO RWY 35C AT DFW DUE TO AN UNSTABLIZED APCH. WE WERE ASKED TO MAINTAIN 4000 FT AND 180 KTS UNTIL FINAL APCH COURSE. THAT PUT US JUST OUTSIDE THE MARKER 1700 FT HIGH AND TOO FAST FOR MORE THAN 20 DEG FLAPS. TRY AS WE MIGHT COULDN'T GET STABILIZED BY 1000 FT, IN FACT WE WOULDN'T HAVE BEEN STABILIZED AT 500 FT EITHER. THE CTLR'S REQUESTS PUT US BEYOND THE CAPABILITIES OF OUR ACFT TO SAFELY FLY THE APCH AND LNDG. WE WENT AROUND AND THE NEXT APCH AND LNDG WERE NORMAL. DFW IS NOTORIOUS FOR LAST MIN RWY CHANGES, WHICH WE GOT, BUT WERE PREPARED FOR BECAUSE THEY ALWAYS DO IT. I KNOW ATC WAS TRYING TO HELP US OUT BY GIVING US A RWY CLOSER TO OUR GATE, BUT WITH THE CONSTRAINTS OF ALT AND AIRSPD PUT US BEYOND THE CAPABILITIES OF OUR ACFT. I'M NOT SURE THEY UNDERSTAND SOME OF OUR LIMITATIONS AND OUR NEED FOR A STABILIZED APCH. OUR MISSED APCH COST US TIME, FUEL, AND PAX FEAR OR DISCOMFORT.
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.