Air carrier flight crew reported being cleared for a night visual to oak runway 30. They were descen...

Narrative:

On the oakes 2 RNAV arrival into oak. Sometime after the toool fix we were cleared direct mitoe; the final approach fix on the ILS 30. We were cleared to 6000 than cleared to 4000. We were always high on this arrival and had the speed brakes deployed most of the time. Soon after clearing us to 4000; the controller asked if we had the oakland airport in sight. We had the airport insight and I thought we were in a position to land so we said we had the airport insight and the controller cleared us to a visual to runway 30. I thought since we had been cleared to 4000 before being cleared for the visual that we were past the parbb fix; one of the initial approach fix on the ILS 30 approach. Instead of holding 4000 longer I put 2700 in the altitude window and started down with the speed brakes deployed. As we started to level off around 2800 feet we get a ground proximity alert and I execute a go around. By the time we leveled off and cleaned the airplane up I decided we were unable to land from the position we were in; the controller started to vector us around for a new approach and landing on 30.at night unable to see terrain should never accept a visual! Should have turned down the clearance direct mitoe and chosen either parbb or frnny.I was notified today and found out two things that happened during this flight that was not included in the previous report. First; there was a flap over speed that I did not enter in the logbook. The reason I did not enter the over speed in the logbook was after the flight the airplane printed out a post flight report that did not list a flap over speed. Based on the post flight report; which I still have; nothing was entered in the logbook. Secondly; I exceeded 250 knots below 10;000 feet. That omission was an oversight.

Original NASA ASRS Text

Title: Air carrier flight crew reported being cleared for a night visual to OAK Runway 30. They were descending towards 2;800 feet after accepting direct to MITOE while still near PARBB. The EGPWS Terrain Warning alerted mandating a go-around which was followed by a vector back to the airport.

Narrative: On the OAKES 2 RNAV Arrival into OAK. Sometime after the TOOOL fix we were cleared direct MITOE; the final approach fix on the ILS 30. We were cleared to 6000 than cleared to 4000. We were always high on this arrival and had the speed brakes deployed most of the time. Soon after clearing us to 4000; the controller asked if we had the Oakland airport in sight. We had the airport insight and I thought we were in a position to land so we said we had the airport insight and the controller cleared us to a visual to runway 30. I thought since we had been cleared to 4000 before being cleared for the visual that we were past the PARBB fix; one of the initial approach fix on the ILS 30 approach. Instead of holding 4000 longer I put 2700 in the altitude window and started down with the speed brakes deployed. As we started to level off around 2800 feet we get a ground proximity alert and I execute a go around. By the time we leveled off and cleaned the airplane up I decided we were unable to land from the position we were in; the controller started to vector us around for a new approach and landing on 30.At night unable to see terrain should never accept a visual! Should have turned down the clearance direct MITOE and chosen either PARBB or FRNNY.I was notified today and found out two things that happened during this flight that was not included in the previous report. First; there was a flap over speed that I did not enter in the logbook. The reason I did not enter the over speed in the logbook was after the flight the airplane printed out a post flight report that did not list a flap over speed. Based on the post flight report; which I still have; nothing was entered in the logbook. Secondly; I exceeded 250 knots below 10;000 feet. That omission was an oversight.

Data retrieved from NASA's ASRS site 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.

Attributes
ACN	1302997
Time
Date	201510
Local Time Of Day	1801-2400
Place
Locale Reference	OAK.Airport
State Reference	CA
Environment
Flight Conditions	VMC
Light	Night
Aircraft 1
Make Model Name	Large Transport Low Wing 2 Turbojet Eng
Operating Under FAR Part	Part 121
Flight Phase	Initial Approach
Route In Use	Visual Approach STAR OAKES 2
Flight Plan	IFR
Person 1
Function	Captain Pilot Flying
Qualification	Flight Crew Air Transport Pilot (ATP)
Person 2
Function	Pilot Not Flying First Officer
Qualification	Flight Crew Air Transport Pilot (ATP)
Events
Anomaly	Deviation - Procedural FAR Deviation - Procedural Published Material / Policy Inflight Event / Encounter Unstabilized Approach Inflight Event / Encounter CFTT / CFIT

Air carrier flight crew reported being cleared for a night visual to oak runway 30. They were descending towards 2;800 feet after accepting direct to mitoe while still near parbb. The egpws terrain warning alerted mandating a go-around which was followed by a vector back to the airport.