 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
B737 with new first officer flew slightly through the final approach course before turning inbound to gain more room to loose altitude. Controller corrected the error and issued a visual approach.
| Attributes | |
| ACN | 357040 |
| Time | |
| Date | 199701 |
| Day | Wed |
| Local Time Of Day | 1201 To 1800 |
| Place | |
| Locale Reference | airport : lbb |
| State Reference | TX |
| Altitude | msl bound lower : 8000 msl bound upper : 8000 |
| Environment | |
| Flight Conditions | VMC |
| Light | Daylight |
| Aircraft 1 | |
| Controlling Facilities | tracon : lbb |
| Operator | common carrier : air carrier |
| Make Model Name | B737 Undifferentiated or Other Model |
| Operating Under FAR Part | Part 121 |
| 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 : 250 flight time total : 9600 flight time type : 5000 |
| ASRS Report | 357040 |
| Person 2 | |
| Affiliation | company : air carrier |
| Function | flight crew : first officer |
| Qualification | pilot : atp |
| Events | |
| Anomaly | non adherence : clearance other spatial deviation |
| Independent Detector | other controllera |
| Resolutory Action | controller : issued new clearance flight crew : returned to intended course or assigned course other |
| Consequence | Other |
| Supplementary | |
| Primary Problem | Flight Crew Human Performance |
| Air Traffic Incident | other |
Narrative:
Descending into lbb in beautiful VMC, new hire first officer flying and too high due to lack of DME (TACAN OTS), using abi VOR DME and known distance between 2 airports to plan descent, but a small calculation error put us about 5000 ft too high for the straight-in to runway 26. I told him to widen out a bit to give himself room to get down. In my haste to coach him through this and help him identify the airport, I forgot to ask approach's permission to change heading a few degrees. The controller corrected my error and cleared us for a visual. There were no known traffic conflicts. I sincerely believe that had I called the airport when I saw it instead of when we both saw it, we would have been cleared for a visual at that time and the widening maneuver would have raised no question at all. I promise to remember to ask first next time.
Original NASA ASRS Text
Title: B737 WITH NEW FO FLEW SLIGHTLY THROUGH THE FINAL APCH COURSE BEFORE TURNING INBOUND TO GAIN MORE ROOM TO LOOSE ALT. CTLR CORRECTED THE ERROR AND ISSUED A VISUAL APCH.
Narrative: DSNDING INTO LBB IN BEAUTIFUL VMC, NEW HIRE FO FLYING AND TOO HIGH DUE TO LACK OF DME (TACAN OTS), USING ABI VOR DME AND KNOWN DISTANCE BTWN 2 ARPTS TO PLAN DSCNT, BUT A SMALL CALCULATION ERROR PUT US ABOUT 5000 FT TOO HIGH FOR THE STRAIGHT-IN TO RWY 26. I TOLD HIM TO WIDEN OUT A BIT TO GIVE HIMSELF ROOM TO GET DOWN. IN MY HASTE TO COACH HIM THROUGH THIS AND HELP HIM IDENT THE ARPT, I FORGOT TO ASK APCH'S PERMISSION TO CHANGE HEADING A FEW DEGS. THE CTLR CORRECTED MY ERROR AND CLRED US FOR A VISUAL. THERE WERE NO KNOWN TFC CONFLICTS. I SINCERELY BELIEVE THAT HAD I CALLED THE ARPT WHEN I SAW IT INSTEAD OF WHEN WE BOTH SAW IT, WE WOULD HAVE BEEN CLRED FOR A VISUAL AT THAT TIME AND THE WIDENING MANEUVER WOULD HAVE RAISED NO QUESTION AT ALL. I PROMISE TO REMEMBER TO ASK FIRST NEXT TIME.
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.