 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Air carrier flight crew reported an event of changing visibilities late in the approach from VMC to IMC with the field and runway in sight throughout the approach and landing.
| Attributes | |
| ACN | 1421944 |
| Time | |
| Date | 201702 |
| Local Time Of Day | 1801-2400 |
| Place | |
| Locale Reference | SLC.Airport |
| State Reference | UT |
| Environment | |
| Flight Conditions | Marginal |
| Light | Night |
| Aircraft 1 | |
| Make Model Name | Medium Large Transport |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Final Approach Initial Approach |
| Route In Use | Visual Approach |
| Flight Plan | IFR |
| Component | |
| Aircraft Component | Microphone |
| Person 1 | |
| Function | Captain Pilot Flying |
| Qualification | Flight Crew Air Transport Pilot (ATP) |
| Person 2 | |
| Function | Pilot Flying Captain |
| Qualification | Flight Crew Air Transport Pilot (ATP) |
| Events | |
| Anomaly | Aircraft Equipment Problem Less Severe Deviation - Procedural FAR Inflight Event / Encounter Weather / Turbulence |
Narrative:
On about a 20 mile final to runway 34L we lost communication with approach. Due to a stuck mike. We switched to tower about 19 miles out and let them know about our losing contact with approach. Shortly thereafter we got the runway in sight and called the visual. Tower cleared us for the visual approach to 34L. Approximately 2 to 4 miles out with easy visual contact with the runway; tower called and said that approach had just called and said the field visibility was now 2 miles; and what did we want to do? The first officer responded that we would continue; due to having the runway easily in sight. My mind was now racing. We had about 30 secs to landing with the runway easily in sight which at the time seemed like the safest course of action. We had no alternate; but I had added an extra 600 lbs. Of contingency fuel; but the vis was now dropping. According to operations we only need 1000 & 1 day or 1000 & 2 at night to cancel IFR; or same if on a charted visual flight procedures (cvfp). But this visual app. Requires 1000 & 3. But I thought there had to be some sort of provision for continuing at this point on the visual app. As long as we had the runway in sight.
Original NASA ASRS Text
Title: Air carrier flight crew reported an event of changing visibilities late in the approach from VMC to IMC with the field and runway in sight throughout the approach and landing.
Narrative: On about a 20 mile final to Runway 34L we lost communication with Approach. due to a stuck mike. We switched to Tower about 19 miles out and let them know about our losing contact with Approach. Shortly thereafter we got the runway in sight and called the visual. Tower cleared us for the Visual Approach to 34L. Approximately 2 to 4 miles out with easy visual contact with the runway; Tower called and said that Approach had just called and said the field Visibility was now 2 miles; and what did we want to do? The First Officer responded that we would continue; due to having the Runway easily in sight. My mind was now racing. We had about 30 secs to landing with the Runway easily in sight which at the time seemed like the safest course of action. We had no alternate; but I had added an extra 600 lbs. of contingency fuel; but the Vis was now dropping. According to Operations we only need 1000 & 1 day or 1000 & 2 at night to cancel IFR; or same if on a Charted Visual Flight Procedures (CVFP). But this Visual App. requires 1000 & 3. But I thought there had to be some sort of provision for continuing at this point on the Visual App. as long as we had the Runway in sight.
Data retrieved from NASA's ASRS site 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.