37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 976415 |
Time | |
Date | 201110 |
Local Time Of Day | 1801-2400 |
Place | |
Locale Reference | MDST.Airport |
State Reference | FO |
Environment | |
Flight Conditions | VMC |
Light | Night |
Aircraft 1 | |
Make Model Name | B737-800 |
Flight Phase | Initial Approach |
Flight Plan | IFR |
Person 1 | |
Function | Pilot Flying Captain |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Person 2 | |
Function | First Officer Pilot Not Flying |
Events | |
Anomaly | Deviation - Procedural Published Material / Policy Inflight Event / Encounter Unstabilized Approach |
Narrative:
Upon checking in with santo domingo control; we were assigned the VOR DME runway 29 approach. ATC then cleared us to a fix that does not appear anywhere on the procedure; therefore I asked the first officer to request direct to the emben intersection. ATC approved our request and cleared us to fly the VOR DME 29 approach with no reference to altitude. As we approached from the northwest; I immediately realized that we would need extra turning room to join the final approach course of 297 degrees because of the approximately 120 degree angle from our heading to the final approach course. I slowed the airplane as much as possible to decrease the turn radius and began a descent from 4;300 ft when on an intercept heading to the final approach course of about 45 degrees. I used poor judgment here because we were not yet established on the 297 degree radial. Flight conditions were VMC with scattered clouds and clear visibility with the ground. I was concerned with making the 2;200 ft altitude at pitik. We did intercept the final approach course before pitik; fully configured and leveling off at 2;200 ft. The auto throttles did a poor job of maintaining airspeed so I advanced power and mistakenly pressed the toga button once. To prevent the throttles from going to toga power; I disconnected the auto throttles just as we began our descent for the dda of 1;200 ft. Now we were fast. I made the necessary corrections and landed without incident in the landing zone. I did consider going around because of the unstable approach rule but thought the better of it because I able to correct the deviations in a timely fashion. Throughout the approach; I always knew exactly where we were and in fact I noticed that we stayed inside of the 130 degree radial. I know this because I had the position button pushed for situational awareness which shows on the navigational display what radial you are on. Both of us had terrain selected. I am disappointed in my performance and vow to never allow myself to be set up for such an occurrence ever again. The correct course of action would have been to either proceed directly to the sgo VOR and fly the procedure turn or fly directly to the perpa intersection and fly the arc. I have learned from this and will never improvise an approach ever again.
Original NASA ASRS Text
Title: A B737-800 flight crew reported being cleared direct to a fix that is not part of the VOR DME 29 approach at MDST. The Captain then requests direct to EMBEN and improvised a procedure turn in order to establish on the in bound course. The unstabilized approach resulted in a successful landing.
Narrative: Upon checking in with Santo Domingo Control; we were assigned the VOR DME Runway 29 approach. ATC then cleared us to a fix that does not appear anywhere on the procedure; therefore I asked the First Officer to request direct to the EMBEN Intersection. ATC approved our request and cleared us to fly the VOR DME 29 approach with no reference to altitude. As we approached from the northwest; I immediately realized that we would need extra turning room to join the final approach course of 297 degrees because of the approximately 120 degree angle from our heading to the final approach course. I slowed the airplane as much as possible to decrease the turn radius and began a descent from 4;300 FT when on an intercept heading to the final approach course of about 45 degrees. I used poor judgment here because we were not yet established on the 297 degree radial. Flight conditions were VMC with scattered clouds and clear visibility with the ground. I was concerned with making the 2;200 FT altitude at PITIK. We did intercept the final approach course before PITIK; fully configured and leveling off at 2;200 FT. The auto throttles did a poor job of maintaining airspeed so I advanced power and mistakenly pressed the TOGA button once. To prevent the throttles from going to TOGA power; I disconnected the auto throttles just as we began our descent for the DDA of 1;200 FT. Now we were fast. I made the necessary corrections and landed without incident in the landing zone. I did consider going around because of the unstable approach rule but thought the better of it because I able to correct the deviations in a timely fashion. Throughout the approach; I always knew exactly where we were and in fact I noticed that we stayed inside of the 130 degree radial. I know this because I had the POS button pushed for situational awareness which shows on the navigational display what radial you are on. Both of us had terrain selected. I am disappointed in my performance and vow to never allow myself to be set up for such an occurrence ever again. The correct course of action would have been to either proceed directly to the SGO VOR and fly the procedure turn or fly directly to the PERPA Intersection and fly the arc. I have learned from this and will never improvise an approach ever again.
Data retrieved from NASA's ASRS site as of April 2012 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.