37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 712687 |
Time | |
Date | 200610 |
Local Time Of Day | 0601 To 1200 |
Place | |
Locale Reference | airport : jax.airport |
State Reference | FL |
Altitude | msl bound lower : 500 msl bound upper : 1000 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | tracon : jax.tracon |
Operator | common carrier : air carrier |
Make Model Name | B737-700 |
Operating Under FAR Part | Part 121 |
Navigation In Use | ils localizer & glide slope : 7 |
Flight Phase | descent : approach |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : air carrier |
Function | flight crew : first officer |
Experience | flight time last 90 days : 264 flight time type : 1000 |
ASRS Report | 712687 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
Experience | flight time last 90 days : 240 |
ASRS Report | 712686 |
Events | |
Anomaly | non adherence : company policies other anomaly other spatial deviation |
Independent Detector | other flight crewa other flight crewb |
Resolutory Action | flight crew : returned to intended or assigned course |
Supplementary | |
Problem Areas | Flight Crew Human Performance Weather |
Primary Problem | Flight Crew Human Performance |
Narrative:
We were inbound to jax with runway 7 advertised on the ATIS. Captain asked for runway 13 to cut down on taxi time. I asked approach controller for runway 13 and he said to expect it. We briefed an ILS to visual runway 13. Checked on with ensuing approach controller and he asked if we'd like ILS runway 7 circle to runway 13 to save some time. Captain said yes and we switched over to that plan with a quick brief (we were expecting a visual approach) of the approach to runway 7 without a lot of discussion regarding the circle or the close proximity of the 2 runways thresholds. We broke out of the overcast and had airport in sight at approximately 1800 ft MSL. The captain continued straight ahead towards runway 7 for 200-300 ft before I asked him if he was still planning on circling to which he replied yes. He then did widen out to the left; but not far enough to be aligned with runway 13 by 500 ft. I failed to tell him that we should go around and he failed to go around. The GPWS also gave us one 'sink rate' warning at approximately 300 ft AGL (with no 'pull up' warning) which also should have caused us to go around. We continued and landed runway 13; both realizing that it was a less than ideal approach. In this case; for the amount of taxi time we were going to save; we should have gone ahead with the advertised runway 7 approach. When we briefed runway 13 we should have probably stuck with it rather than switching back to runway 7 with a circling approach. When we switched back to runway 7 we should have just done a straight-in approach since the last min aspect caused us to make some errors with the circle. As pilot monitoring I definitely will step up my level of assertiveness in questioning the captain when I see something that he or she is missing. My experience level with circling approachs is limited and while I thought we needed to make some changes I allowed myself to fall victim to the thought that 'the captain must know what he is doing -- he has more experience; etc.
Original NASA ASRS Text
Title: A B737-700 ON A CIRCLING APCH TO JAX WAS SLOW TO GET LINED UP AND STABILIZED; GETTING A 'SINK RATE' GPWS AT ONE POINT. THEY CONTINUED AND LANDED.
Narrative: WE WERE INBOUND TO JAX WITH RWY 7 ADVERTISED ON THE ATIS. CAPT ASKED FOR RWY 13 TO CUT DOWN ON TAXI TIME. I ASKED APCH CTLR FOR RWY 13 AND HE SAID TO EXPECT IT. WE BRIEFED AN ILS TO VISUAL RWY 13. CHKED ON WITH ENSUING APCH CTLR AND HE ASKED IF WE'D LIKE ILS RWY 7 CIRCLE TO RWY 13 TO SAVE SOME TIME. CAPT SAID YES AND WE SWITCHED OVER TO THAT PLAN WITH A QUICK BRIEF (WE WERE EXPECTING A VISUAL APCH) OF THE APCH TO RWY 7 WITHOUT A LOT OF DISCUSSION REGARDING THE CIRCLE OR THE CLOSE PROX OF THE 2 RWYS THRESHOLDS. WE BROKE OUT OF THE OVCST AND HAD ARPT IN SIGHT AT APPROX 1800 FT MSL. THE CAPT CONTINUED STRAIGHT AHEAD TOWARDS RWY 7 FOR 200-300 FT BEFORE I ASKED HIM IF HE WAS STILL PLANNING ON CIRCLING TO WHICH HE REPLIED YES. HE THEN DID WIDEN OUT TO THE L; BUT NOT FAR ENOUGH TO BE ALIGNED WITH RWY 13 BY 500 FT. I FAILED TO TELL HIM THAT WE SHOULD GO AROUND AND HE FAILED TO GO AROUND. THE GPWS ALSO GAVE US ONE 'SINK RATE' WARNING AT APPROX 300 FT AGL (WITH NO 'PULL UP' WARNING) WHICH ALSO SHOULD HAVE CAUSED US TO GO AROUND. WE CONTINUED AND LANDED RWY 13; BOTH REALIZING THAT IT WAS A LESS THAN IDEAL APCH. IN THIS CASE; FOR THE AMOUNT OF TAXI TIME WE WERE GOING TO SAVE; WE SHOULD HAVE GONE AHEAD WITH THE ADVERTISED RWY 7 APCH. WHEN WE BRIEFED RWY 13 WE SHOULD HAVE PROBABLY STUCK WITH IT RATHER THAN SWITCHING BACK TO RWY 7 WITH A CIRCLING APCH. WHEN WE SWITCHED BACK TO RWY 7 WE SHOULD HAVE JUST DONE A STRAIGHT-IN APCH SINCE THE LAST MIN ASPECT CAUSED US TO MAKE SOME ERRORS WITH THE CIRCLE. AS PLT MONITORING I DEFINITELY WILL STEP UP MY LEVEL OF ASSERTIVENESS IN QUESTIONING THE CAPT WHEN I SEE SOMETHING THAT HE OR SHE IS MISSING. MY EXPERIENCE LEVEL WITH CIRCLING APCHS IS LIMITED AND WHILE I THOUGHT WE NEEDED TO MAKE SOME CHANGES I ALLOWED MYSELF TO FALL VICTIM TO THE THOUGHT THAT 'THE CAPT MUST KNOW WHAT HE IS DOING -- HE HAS MORE EXPERIENCE; ETC.
Data retrieved from NASA's ASRS site as of January 2009 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.