Date: 201510
Local time of day: 0001-0600
Location: OAK.Airport, CA
Flight conditions: VMC
Weather elements / visibility: 5
Light: Night
Aircraft: B767-300 and 300 ER
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Cargo / Freight / Delivery
Flight phase: Initial Approach
Airspace: Class C OAK
ATC / advisory: Tower OAK
Reporter organization: Air Carrier
Reporter function: Pilot Flying; First Officer
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Situational Awareness
Second reporter function: Pilot Not Flying; Captain
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Inflight Event / Encounter CFTT / CFIT
Detector: Automation Aircraft Terrain Warning; Person Flight Crew
When detected: In-flight
Result: Flight Crew Became Reoriented; Flight Crew Took Evasive Action
Contributing factors: Human Factors; Procedure
Primary problem: Human Factors

Narrative: As the pilot flying; I was cleared off the OAKES2 arrival and cleared direct to MITOE initially to 6000 ft for the visually approach to Rwy 30. Approach then cleared us to 4000 ft and said the airport was at 1 o'clock. We reported the airport in sight. After reporting the field in sight; ATC cleared us for the visual approach to Rwy 30. The WX was clear and the visibility was unrestricted. I flew the approach with Terrain mode selected on the radar and was aware of the terrain southeast of final approach course to Rwy 30 (as noted also in the 10-10 page). I used FLCH for the descent mode upon being cleared direct to MITOE and no longer on the arrival into Oakland. The descent rate was approximately 1000-1500 FPM and I was slowing/configuring the aircraft as we approached 5NM from MITOE. During the descent; I was monitoring the 'green arc' and clearing visually to ensure I was clear of the terrain while trying to achieve a 2000 ft MSL level-off at MITOE. I also had the ILS selected to back-up the approach; aid in the intercept and aid in the descent to Rwy 30. Approximately; 2.5 NM from MITOE; we received a momentary GPWS 'Terrain' warning as we passed over the terrain southeast of the approach course on an intercept heading to MITOE. Upon hearing the warning; I took positive immediate corrective action by disconnecting the autopilot and arresting my descent. Because the GPWS warning was momentary; by the time I disconnected the autopilot and arrested the descent; the warning ceased and we were clear of the terrain. The altitude in the radar altimeter was increasing and we were still stabilized approaching MITOE. I elected to cease the maneuver and continue normal flight profile for the approach. As we intercepted final approach at MITOE; we were configured; on speed and slightly above glide path (with reference to the ILS). I intercepted glide path just past MITOE and was stabilized for the approach. We landed at Oakland with no further incident. With reference to the CFIT escape; a full maneuver was not accomplished. Due to the terrain in question and flight profile; upon disconnecting the autopilot and arresting the descent the warning ceased. The GPWS warning was momentary in nature. We were clear of terrain and still within safe parameters to continue the visual approach. I elected to cease the maneuver and continue the flight profile for the approach. At no time did the radar display any 'yellow' or 'red' indications for terrain and we had the ridge line insight.  The lesson learned from this event is often times ATC will clear you for the visual approach when WX conditions are favorable. I could have modified my approach to intercept final further out allowing me to maintain a higher altitude over the terrain and still maintain stabilized parameters for the approach. However; due to other factors involved (note in the 10-10 page about terrain; night conditions; etc.); it would have been best remain on the arrival and ILS approach to avoid the terrain altogether.


Second narrative: On arrival we were cleared down to 4000 feet and cleared direct to the FAF MITOE RWY 30 OAK. At about 20 miles from field; approach asked if we had the airport in sight. FO was the PF. We confirmed that we had the field in sight and at that time we were cleared for the visual approach to 30. At that time since we were heading direct to MITOE the FAF altitude of 2000 feet was put in the MCP. Per the 10-10 page the FO and myself were aware of terrain in the area and both of us had terrain displayed; and monitoring. On our descent both of us were monitoring closely our terrain display and referencing our green arc which showed us arriving at MITOE at 2000 feet. As a secondary descent reference we had the G/S too; which showed us slightly high. At no time did our terrain display show anything but a spattering of green and never any yellow or red. As we were almost clear of the ridge we encountered a EGPWS warning of terrain and to climb. At that time the FO started to execute our CFIT maneuver by disengaging the autopilot and stopping our descent. Almost immediately after disconnecting the autopilot we were clear of terrain and no climb was necessary. We continued on our descent to MITOE and landed without issue. During this whole encounter we had the ridge line and airport insight. It is also interesting to note that ATC never indicated any low altitude alert.


Synopsis: B767 flight were experienced a GPWS terrain warning during a night visual approach to Runway 30 at OAK. The crew was on the OAKES2 Arrival; had been cleared direct MITOE; and cleared for the visual; but did not stay with the OAKES crossing restrictions. The warning was momentary and the terrain avoidance maneuver was barely started when the warning ceased.