37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1614860 |
Time | |
Date | 201902 |
Local Time Of Day | 1201-1800 |
Place | |
Locale Reference | MSO.Airport |
State Reference | MT |
Environment | |
Flight Conditions | VMC |
Aircraft 1 | |
Make Model Name | Commercial Fixed Wing |
Operating Under FAR Part | Part 121 |
Flight Phase | Final Approach |
Flight Plan | IFR |
Person 1 | |
Function | Pilot Not Flying Captain |
Qualification | Flight Crew Multiengine Flight Crew Air Transport Pilot (ATP) Flight Crew Instrument |
Experience | Flight Crew Last 90 Days 350 Flight Crew Total 23000 Flight Crew Type 8132 |
Person 2 | |
Function | First Officer Pilot Flying |
Qualification | Flight Crew Instrument Flight Crew Air Transport Pilot (ATP) Flight Crew Multiengine |
Events | |
Anomaly | Deviation - Procedural Published Material / Policy Inflight Event / Encounter Unstabilized Approach Inflight Event / Encounter CFTT / CFIT |
Narrative:
I have flown into missoula multiple times this winter. Missoula can be a challenging airport to fly into. On my previous flights I have used the ILS to runway 12 because of the IFR conditions and night arrivals. Today we were expecting a visual to runway 30. The conditions were VFR with high ceilings and excellent visibility. We had the airport in sight about 60 miles out. Because this was the first time that either of us had attempted this approach we did an extensive briefing and set up the FMC for the approach. We flew the VOR-B approach and then transitioned to the visual approach. The first officer (first officer) was flying and configured early hitting all the target speeds and altitudes until we turned about 2 mile final. There was some confusion on that segment of the approach regarding descent technique which resulted in us being approximately 500 feet high. At that point the first officer suggested that we go around. We were on speed completely configured with the checklist completed and I thought we could still meet our stabilization criteria so I pushed him to continue. This was my first poor decision. At my urging he increased the descent rate and we got up to 3 sink rates each corrected immediately. By 500 feet I perceived that we had caught our glide path which resulted in a landing in the touchdown zone albeit a little fast. We exited the runway at A4 for a normal taxi to the gate.
Original NASA ASRS Text
Title: Air Carrier flight crew reported continuing an unstabilized approach into MSO even after receiving three 'sink rate' advisories.
Narrative: I have flown into Missoula multiple times this winter. Missoula can be a challenging airport to fly into. On my previous flights I have used the ILS to runway 12 because of the IFR conditions and night arrivals. Today we were expecting a visual to runway 30. The conditions were VFR with high ceilings and excellent visibility. We had the airport in sight about 60 miles out. Because this was the first time that either of us had attempted this approach we did an extensive briefing and set up the FMC for the approach. We flew the VOR-B approach and then transitioned to the visual approach. The FO (First Officer) was flying and configured early hitting all the target speeds and altitudes until we turned about 2 mile final. There was some confusion on that segment of the approach regarding descent technique which resulted in us being approximately 500 feet high. At that point the FO suggested that we go around. We were on speed completely configured with the checklist completed and I thought we could still meet our stabilization criteria so I pushed him to continue. This was my first poor decision. At my urging he increased the descent rate and we got up to 3 sink rates each corrected immediately. By 500 feet I perceived that we had caught our glide path which resulted in a landing in the touchdown zone albeit a little fast. We exited the runway at A4 for a normal taxi to the gate.
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.