37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1149658 |
Time | |
Date | 201402 |
Local Time Of Day | 1801-2400 |
Place | |
Locale Reference | OAK.Airport |
State Reference | CA |
Aircraft 1 | |
Make Model Name | A320 |
Operating Under FAR Part | Part 121 |
Flight Phase | Final Approach |
Flight Plan | IFR |
Person 1 | |
Function | Approach |
Qualification | Air Traffic Control Fully Certified |
Experience | Air Traffic Control Time Certified In Pos 1 (yrs) 7 |
Events | |
Anomaly | Deviation - Altitude Crossing Restriction Not Met Deviation - Altitude Overshoot Deviation - Track / Heading All Types Inflight Event / Encounter CFTT / CFIT |
Narrative:
I was working the mulford/grove combined sector for the oakland final on an odd configuration. No aircraft could land on our long runway; runway 30; and we were forced to land air carriers on our shorter runways; runways 28 left and right. An A320 was cleared for the RNAV runway 28L approach into oak; about 7 miles from jupap; told to cross jupap at or above 3;700 as published. About a mile prior to jupap the A320 started a right turn about 10-20 degrees right of course but continued to descend as if on the profile. I told the A320 he appeared right of course and to say intentions. The A320 indicated he was turning back to course; I observed him descend below the MVA and still heading right of course not correcting. I issued a low altitude alert; climbed the A320 to the MVA and then resequenced him for the ILS runway 28R. The A320 landed without incident. I was later informed that a pilot deviation was filed against the pilot; which I do not think is necessary. Also to note is that I believe this was during a period where we had notams out for GPS unreliable; but I cannot confirm because accurate records are not kept for when notams are canceled. I do not have a fix recommendation as I still do not know why the error occurred.
Original NASA ASRS Text
Title: NCT Controller reports an A320 crew descending early and deviating from the RNAV (GPS) Y Runway 28L course during approach to OAK. The crew is queried then issued a low altitude alert and the approach is continued to landing. A NOTAM for GPS unreliable may have been in effect at the time of the incident.
Narrative: I was working the Mulford/Grove combined sector for the Oakland final on an odd configuration. No aircraft could land on our long runway; Runway 30; and we were forced to land air carriers on our shorter runways; runways 28 left and right. An A320 was cleared for the RNAV Runway 28L approach into OAK; about 7 miles from JUPAP; told to cross JUPAP at or above 3;700 as published. About a mile prior to JUPAP the A320 started a right turn about 10-20 degrees right of course but continued to descend as if on the profile. I told the A320 he appeared right of course and to say intentions. The A320 indicated he was turning back to course; I observed him descend below the MVA and still heading right of course not correcting. I issued a Low Altitude Alert; climbed the A320 to the MVA and then resequenced him for the ILS Runway 28R. The A320 landed without incident. I was later informed that a pilot deviation was filed against the pilot; which I do not think is necessary. Also to note is that I believe this was during a period where we had NOTAMs out for GPS unreliable; but I cannot confirm because accurate records are not kept for when NOTAMs are canceled. I do not have a fix recommendation as I still do not know why the error occurred.
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.