37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 305007 |
Time | |
Date | 199505 |
Day | Sun |
Local Time Of Day | 0601 To 1200 |
Place | |
Locale Reference | airport : sfo |
State Reference | CA |
Altitude | msl bound lower : 2500 msl bound upper : 2500 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | tracon : oak |
Operator | common carrier : air carrier |
Make Model Name | Any Unknown or Unlisted Aircraft Manufacturer |
Operating Under FAR Part | Part 121 |
Navigation In Use | Other Other |
Flight Phase | descent : approach landing other |
Route In Use | arrival other |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
Qualification | pilot : atp |
Experience | flight time total : 20000 |
ASRS Report | 305007 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : first officer |
Qualification | pilot : instrument pilot : commercial |
Events | |
Anomaly | other anomaly other other anomaly other |
Independent Detector | other flight crewa |
Resolutory Action | other other |
Consequence | Other |
Supplementary | |
Air Traffic Incident | other other |
Narrative:
I feel that this (lda) is a high workload and stressful approach in the best of circumstances. But with approach control excessively vectoring and changing the assigned approach too close to FAF, it made it potentially unsafe. There was too little time to retune radios, identify the lda, ILS, OM, etc, talk to approach and tower, configure, checklist, flight attendant notification, etc. Next time I will either refuse the lda entirely, or refuse any multiple deviations and/or changes from initial clearance. While we met all qualification for stabilized approach, ie, configured, etc, had anything further out of the ordinary occurred, in my opinion it would have pushed the arrival beyond a safe threshold. I am withholding judgement on the appropriateness of the lda DME runway 28R itself until I see some more, but recommend that ATC minimize any deviation from a routine approach.
Original NASA ASRS Text
Title: APCH EVALUATION.
Narrative: I FEEL THAT THIS (LDA) IS A HIGH WORKLOAD AND STRESSFUL APCH IN THE BEST OF CIRCUMSTANCES. BUT WITH APCH CTL EXCESSIVELY VECTORING AND CHANGING THE ASSIGNED APCH TOO CLOSE TO FAF, IT MADE IT POTENTIALLY UNSAFE. THERE WAS TOO LITTLE TIME TO RETUNE RADIOS, IDENT THE LDA, ILS, OM, ETC, TALK TO APCH AND TWR, CONFIGURE, CHKLIST, FLT ATTENDANT NOTIFICATION, ETC. NEXT TIME I WILL EITHER REFUSE THE LDA ENTIRELY, OR REFUSE ANY MULTIPLE DEVS AND/OR CHANGES FROM INITIAL CLRNC. WHILE WE MET ALL QUALIFICATION FOR STABILIZED APCH, IE, CONFIGURED, ETC, HAD ANYTHING FURTHER OUT OF THE ORDINARY OCCURRED, IN MY OPINION IT WOULD HAVE PUSHED THE ARR BEYOND A SAFE THRESHOLD. I AM WITHHOLDING JUDGEMENT ON THE APPROPRIATENESS OF THE LDA DME RWY 28R ITSELF UNTIL I SEE SOME MORE, BUT RECOMMEND THAT ATC MINIMIZE ANY DEV FROM A ROUTINE APCH.
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.