 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
A B737 flight crew attempts a difficult and illegal approach when the approach controller vectors them too close to the LOM at bwi, md. Aircraft lands without landing clearance.
| Attributes | |
| ACN | 439918 |
| Time | |
| Date | 199906 |
| Day | Thu |
| Local Time Of Day | 1201 To 1800 |
| Place | |
| Locale Reference | airport : bwi.airport |
| State Reference | MD |
| Altitude | agl single value : 0 |
| Environment | |
| Flight Conditions | Mixed |
| Light | Daylight |
| Aircraft 1 | |
| Controlling Facilities | tower : bwi.tower |
| Operator | common carrier : air carrier |
| Make Model Name | B737 Undifferentiated or Other Model |
| Operating Under FAR Part | Part 121 |
| Navigation In Use | ils localizer & glide slope : 10 |
| Flight Phase | landing : roll |
| Route In Use | approach : instrument precision |
| Flight Plan | IFR |
| Person 1 | |
| Affiliation | company : air carrier |
| Function | flight crew : captain oversight : pic |
| Qualification | pilot : atp |
| Experience | flight time last 90 days : 220 flight time total : 9000 |
| ASRS Report | 439918 |
| Person 2 | |
| Affiliation | company : air carrier |
| Function | flight crew : first officer |
| Qualification | pilot : multi engine pilot : flight engineer pilot : atp |
| Experience | flight time last 90 days : 5 flight time total : 16000 flight time type : 10 |
| ASRS Report | 439763 |
| Events | |
| Anomaly | incursion : landing without clearance incursion : runway non adherence : published procedure non adherence : far non adherence : company policies non adherence : clearance other anomaly |
| Independent Detector | other flight crewa other flight crewb |
| Resolutory Action | none taken : anomaly accepted |
| Supplementary | |
| Problem Areas | ATC Human Performance Environmental Factor Flight Crew Human Performance |
| Primary Problem | ATC Human Performance |
| Air Traffic Incident | Pilot Deviation |
Narrative:
On approach to bwi, we were being vectored for an ILS approach to runway 10R from the south. There was very heavy frequency chatter and traffic. Approach 'will be a vector through the 'localizer to intercept from north.' crossed localizer to the north side at about 12 NM, then a 'turn to 130 degrees to intercept, maintain 2000 ft until established on localizer, cleared for approach.' at 6 DME, localizer still not off case. Inside 5 NM, localizer off case, began descent to capture GS from above, complete aircraft landing confign, etc. Still heavy frequency chatter. Cockpit events: can't descend till localizer, got to get down to GS, etc, believe we can make it! Never cleared to tower! Can we make it safely? Yes, we'll make it, but close! On rollout, approach control, 'contact tower!' realized our error, cleared runway as quickly as possible on runway 22/4 short runway (we were briefed 2 weeks earlier that runway 22/4 was basically closed and could normally plan to use it to clear runway). Contacted ground to taxi to gate. Factors: 1) WX -- heavy approach chatter/workload. Held high, steep descent through WX on short approach. 2) got to get down or go missed, got to get it done. 3) never told to contact tower (no excuse on our part) but heavy task loading to complete the approach, distraction from normal. Corrections: not try to run approachs too close to other aircraft nor out in tight to the approach. On our part, stay focused on all the mission, don't get complacent. Supplemental information from acn 439763: broke out of clouds. Had visual contact with runway. We elected to exit the runway onto a little used runway after assuring it was clear, due to traffic on short final behind us. Attempted to contact ground control as we exited but due to congestion could not reach for several seconds.
Original NASA ASRS Text
Title: A B737 FLC ATTEMPTS A DIFFICULT AND ILLEGAL APCH WHEN THE APCH CTLR VECTORS THEM TOO CLOSE TO THE LOM AT BWI, MD. ACFT LANDS WITHOUT LNDG CLRNC.
Narrative: ON APCH TO BWI, WE WERE BEING VECTORED FOR AN ILS APCH TO RWY 10R FROM THE S. THERE WAS VERY HVY FREQ CHATTER AND TFC. APCH 'WILL BE A VECTOR THROUGH THE 'LOC TO INTERCEPT FROM N.' CROSSED LOC TO THE N SIDE AT ABOUT 12 NM, THEN A 'TURN TO 130 DEGS TO INTERCEPT, MAINTAIN 2000 FT UNTIL ESTABLISHED ON LOC, CLRED FOR APCH.' AT 6 DME, LOC STILL NOT OFF CASE. INSIDE 5 NM, LOC OFF CASE, BEGAN DSCNT TO CAPTURE GS FROM ABOVE, COMPLETE ACFT LNDG CONFIGN, ETC. STILL HVY FREQ CHATTER. COCKPIT EVENTS: CAN'T DSND TILL LOC, GOT TO GET DOWN TO GS, ETC, BELIEVE WE CAN MAKE IT! NEVER CLRED TO TWR! CAN WE MAKE IT SAFELY? YES, WE'LL MAKE IT, BUT CLOSE! ON ROLLOUT, APCH CTL, 'CONTACT TWR!' REALIZED OUR ERROR, CLRED RWY AS QUICKLY AS POSSIBLE ON RWY 22/4 SHORT RWY (WE WERE BRIEFED 2 WKS EARLIER THAT RWY 22/4 WAS BASICALLY CLOSED AND COULD NORMALLY PLAN TO USE IT TO CLR RWY). CONTACTED GND TO TAXI TO GATE. FACTORS: 1) WX -- HVY APCH CHATTER/WORKLOAD. HELD HIGH, STEEP DSCNT THROUGH WX ON SHORT APCH. 2) GOT TO GET DOWN OR GO MISSED, GOT TO GET IT DONE. 3) NEVER TOLD TO CONTACT TWR (NO EXCUSE ON OUR PART) BUT HVY TASK LOADING TO COMPLETE THE APCH, DISTR FROM NORMAL. CORRECTIONS: NOT TRY TO RUN APCHS TOO CLOSE TO OTHER ACFT NOR OUT IN TIGHT TO THE APCH. ON OUR PART, STAY FOCUSED ON ALL THE MISSION, DON'T GET COMPLACENT. SUPPLEMENTAL INFO FROM ACN 439763: BROKE OUT OF CLOUDS. HAD VISUAL CONTACT WITH RWY. WE ELECTED TO EXIT THE RWY ONTO A LITTLE USED RWY AFTER ASSURING IT WAS CLR, DUE TO TFC ON SHORT FINAL BEHIND US. ATTEMPTED TO CONTACT GND CTL AS WE EXITED BUT DUE TO CONGESTION COULD NOT REACH FOR SEVERAL SECONDS.
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.