Crj-700 flight crew reported while on approach to runway 27 at san they deviated from the localizer ...

Attributes
ACN	1100731
Time
Date	201307
Local Time Of Day	0601-1200
Place
Locale Reference	SAN.Airport
State Reference	CA
Environment
Light	Daylight
Aircraft 1
Make Model Name	Regional Jet 700 ER/LR (CRJ700)
Operating Under FAR Part	Part 121
Flight Phase	Initial Approach
Flight Plan	IFR
Person 1
Function	Captain Pilot Not Flying
Qualification	Flight Crew Air Transport Pilot (ATP)
Person 2
Function	First Officer Pilot Flying
Qualification	Flight Crew Commercial
Events
Anomaly	Deviation - Altitude Excursion From Assigned Altitude Deviation - Procedural Published Material / Policy Deviation - Procedural Clearance Inflight Event / Encounter CFTT / CFIT

Narrative:

While being vectored for the approach the final approach controller left us high and gave us a short vector for the canpa approach. While intercepting the localizer I realized that we were not tracking the localizer inbound. I verified the localizer frequency in both the active nav 1 and nav 2 frequencies. At this point the pilot flying (first officer) disconnected the autopilot while we discussed the problem and began to mention the possibility of going around. The tower controller then gave us a low altitude alert. I told the controller that we were correcting. At this point we made the decision to execute a go-around. We began the go-around and I told the controller we were going around. Cause: focusing too much on intercepting the course and not properly monitoring the approach. After experiencing this circumstance; I would ask for a longer approach where we didn't feel rushed to get down and get configured. If we had had another 3-5 miles on the approach I believe that we would not have had this problem.

Original NASA ASRS Text

Title: CRJ-700 flight crew reported while on approach to Runway 27 at SAN they deviated from the localizer during a rushed approach and were given a low altitude warning from ATC; which triggered a go-around.

Narrative: While being vectored for the approach the Final Approach Controller left us high and gave us a short vector for the CANPA approach. While intercepting the localizer I realized that we were not tracking the localizer inbound. I verified the localizer frequency in both the active Nav 1 and Nav 2 frequencies. At this point the pilot flying (First Officer) disconnected the autopilot while we discussed the problem and began to mention the possibility of going around. The Tower Controller then gave us a low altitude alert. I told the Controller that we were correcting. At this point we made the decision to execute a go-around. We began the go-around and I told the Controller we were going around. Cause: Focusing too much on intercepting the course and not properly monitoring the approach. After experiencing this circumstance; I would ask for a longer approach where we didn't feel rushed to get down and get configured. If we had had another 3-5 miles on the approach I believe that we would not have had this problem.

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

Crj-700 flight crew reported while on approach to runway 27 at san they deviated from the localizer during a rushed approach and were given a low altitude warning from ATC; which triggered a go-around.