 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
B737-300 crew and another company aircraft both executed egpws escape maneuvers with an emergency maximum rate climb until the warning stopped. Both aircraft were at minimum vectoring altitude at the time of occurrence.
| Attributes | |
| ACN | 537528 |
| Time | |
| Date | 200202 |
| Day | Thu |
| Local Time Of Day | 1801 To 2400 |
| Place | |
| Locale Reference | intersection : locke |
| State Reference | CA |
| Altitude | msl single value : 5000 |
| Environment | |
| Flight Conditions | IMC |
| Weather Elements | Rain Turbulence other |
| Light | Night |
| Aircraft 1 | |
| Controlling Facilities | tracon : o90.tracon |
| Operator | common carrier : air carrier |
| Make Model Name | B737-300 |
| Operating Under FAR Part | Part 121 |
| Navigation In Use | ils localizer & glide slope : 11 |
| Flight Phase | descent : approach |
| Route In Use | approach : instrument precision arrival : on vectors |
| Flight Plan | IFR |
| Aircraft 2 | |
| Controlling Facilities | tracon : o90.tracon |
| 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 : 11 |
| Flight Phase | descent : approach |
| Route In Use | approach : instrument precision departure : on vectors |
| Flight Plan | IFR |
| Person 1 | |
| Affiliation | company : air carrier |
| Function | flight crew : captain oversight : pic |
| Qualification | pilot : atp |
| Experience | flight time last 90 days : 240 flight time total : 15000 flight time type : 11000 |
| ASRS Report | 537528 |
| Person 2 | |
| Affiliation | company : air carrier |
| Function | flight crew : first officer |
| Qualification | pilot : commercial pilot : instrument pilot : multi engine |
| Experience | flight time last 90 days : 215 flight time total : 14500 flight time type : 3400 |
| ASRS Report | 537533 |
| Events | |
| Anomaly | inflight encounter : turbulence inflight encounter : weather inflight encounter other other anomaly other other spatial deviation |
| Independent Detector | aircraft equipment : gpws other flight crewa other flight crewb other other : 4 |
| Resolutory Action | flight crew : took evasive action none taken : detected after the fact other |
| Consequence | faa : reviewed incident with flight crew other |
| Supplementary | |
| Problem Areas | Aircraft FAA Weather |
Narrative:
Terrain warning. This report is being submitted to identify a 'general or specific' flight safety concern. The aircrew followed/flew established procedures. Our flight was originally assigned the commo arrival. At volta we were instructed to proceed direct locke. Approaching locke another vector was assigned for downwind to the ILS runway 11. WX-IMC/rain/light turbulence. Aircraft was established on an assigned altitude of 5000 ft. An egpws warning for terrain was received, 'terrain-terrain' (only one cycle of warning). Procedures immediately followed, 15-20 degree nose high climb initiated. MSA for our area noted at 5100 ft, and level off completed at 6000 ft. Approach control was notified of the warning/climb at approximately 5500 ft. Approach was continued to an uneventful landing. Time of occurrence XA55Z-location-over mt. Diablo (both time and exact location provided by bay approach control). I spoke to the bay approach control operations manager/supervisor after landing. He could offer no explanation for the warning, but did give me the time/location, stated there had been no traffic conflict as a result of our climb and that another company flight, immediately following our aircraft, had also received a terrain warning in the same location. He also noted that bay approach would not submit any 'traffic conflict report' or other deviation report, only that the occurrence had been entered in his activity log for the purpose of identifying what problem may exist. I spoke to the company safety rep in the a.M. Of 02/feb/02 about the above occurrence, and that two of our aircraft had experienced the same occurrence. He advised me to submit an irregularity report and a safety report. Supplemental information from acn 537533: this report is being submitted to identify a flight safety concern. Our flight was originally assigned commo arrival. At volta we were instructed to proceed direct locke. 5 min after we were given vectors and dscnts for ILS runway 11 oak. We were IMC at level 5000 when we got a 'terrain warning'. We began a climb and let ATC know we were climbing for a terrain warning and we would level at 6000 ft. We continued the flight to an uneventful landing. After landing the captain spoke to bay approach. He could offer no explanation for the warning. He gave us the time and location and stated there had been no traffic conflict as a result of our climb. He also said the bay approach would not submit any 'traffic conflict report' or other deviation report.
Original NASA ASRS Text
Title: B737-300 CREW AND ANOTHER COMPANY ACFT BOTH EXECUTED EGPWS ESCAPE MANEUVERS WITH AN EMER MAX RATE CLB UNTIL THE WARNING STOPPED. BOTH ACFT WERE AT MINIMUM VECTORING ALT AT THE TIME OF OCCURRENCE.
Narrative: TERRAIN WARNING. THIS RPT IS BEING SUBMITTED TO IDENTIFY A 'GENERAL OR SPECIFIC' FLT SAFETY CONCERN. THE AIRCREW FOLLOWED/FLEW ESTABLISHED PROCEDURES. OUR FLT WAS ORIGINALLY ASSIGNED THE COMMO ARRIVAL. AT VOLTA WE WERE INSTRUCTED TO PROCEED DIRECT LOCKE. APCHING LOCKE ANOTHER VECTOR WAS ASSIGNED FOR DOWNWIND TO THE ILS RWY 11. WX-IMC/RAIN/LIGHT TURBULENCE. ACFT WAS ESTABLISHED ON AN ASSIGNED ALTITUDE OF 5000 FT. AN EGPWS WARNING FOR TERRAIN WAS RECEIVED, 'TERRAIN-TERRAIN' (ONLY ONE CYCLE OF WARNING). PROCEDURES IMMEDIATELY FOLLOWED, 15-20 DEG NOSE HIGH CLB INITIATED. MSA FOR OUR AREA NOTED AT 5100 FT, AND LEVEL OFF COMPLETED AT 6000 FT. APCH CTL WAS NOTIFIED OF THE WARNING/CLB AT APPROX 5500 FT. APCH WAS CONTINUED TO AN UNEVENTFUL LNDG. TIME OF OCCURRENCE XA55Z-LOCATION-OVER MT. DIABLO (BOTH TIME AND EXACT LOCATION PROVIDED BY BAY APCH CTL). I SPOKE TO THE BAY APCH CTL OPS MGR/SUPVR AFTER LNDG. HE COULD OFFER NO EXPLANATION FOR THE WARNING, BUT DID GIVE ME THE TIME/LOCATION, STATED THERE HAD BEEN NO TFC CONFLICT AS A RESULT OF OUR CLB AND THAT ANOTHER COMPANY FLT, IMMEDIATELY FOLLOWING OUR ACFT, HAD ALSO RECEIVED A TERRAIN WARNING IN THE SAME LOCATION. HE ALSO NOTED THAT BAY APCH WOULD NOT SUBMIT ANY 'TFC CONFLICT RPT' OR OTHER DEVIATION RPT, ONLY THAT THE OCCURRENCE HAD BEEN ENTERED IN HIS ACTIVITY LOG FOR THE PURPOSE OF IDENTIFYING WHAT PROBLEM MAY EXIST. I SPOKE TO THE COMPANY SAFETY REP IN THE A.M. OF 02/FEB/02 ABOUT THE ABOVE OCCURRENCE, AND THAT TWO OF OUR ACFT HAD EXPERIENCED THE SAME OCCURRENCE. HE ADVISED ME TO SUBMIT AN IRREGULARITY RPT AND A SAFETY RPT. SUPPLEMENTAL INFO FROM ACN 537533: THIS RPT IS BEING SUBMITTED TO IDENTIFY A FLT SAFETY CONCERN. OUR FLT WAS ORIGINALLY ASSIGNED COMMO ARRIVAL. AT VOLTA WE WERE INSTRUCTED TO PROCEED DIRECT LOCKE. 5 MIN AFTER WE WERE GIVEN VECTORS AND DSCNTS FOR ILS RWY 11 OAK. WE WERE IMC AT LEVEL 5000 WHEN WE GOT A 'TERRAIN WARNING'. WE BEGAN A CLB AND LET ATC KNOW WE WERE CLBING FOR A TERRAIN WARNING AND WE WOULD LEVEL AT 6000 FT. WE CONTINUED THE FLT TO AN UNEVENTFUL LNDG. AFTER LNDG THE CAPT SPOKE TO BAY APCH. HE COULD OFFER NO EXPLANATION FOR THE WARNING. HE GAVE US THE TIME AND LOCATION AND STATED THERE HAD BEEN NO TFC CONFLICT AS A RESULT OF OUR CLB. HE ALSO SAID THE BAY APCH WOULD NOT SUBMIT ANY 'TFC CONFLICT RPT' OR OTHER DEVIATION RPT.
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.