37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1082532 |
Time | |
Date | 201304 |
Local Time Of Day | 1801-2400 |
Place | |
Locale Reference | RIC.Airport |
State Reference | VA |
Environment | |
Flight Conditions | VMC |
Aircraft 1 | |
Make Model Name | EMB ERJ 145 ER/LR |
Operating Under FAR Part | Part 121 |
Flight Phase | Initial Approach |
Person 1 | |
Function | First Officer Pilot Flying |
Events | |
Anomaly | ATC Issue All Types Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy Deviation - Track / Heading All Types Inflight Event / Encounter Unstabilized Approach |
Narrative:
Approaching ric; we were expecting the visual approach to runway 2. We were speaking to pct at 2;000 ft. We were given direct to the airport. I had noticed that we were 5 miles from the airport with no approach clearance. Upon reaching 4 miles from the airport; we were cleared for the visual approach to runway 2; after calling it in sight. However; we were approaching the airport at 200 KTS and not configured for landing. After getting configured and making our own vectors; we were on a left base for runway 2; but too close to make an approach to landing; so we told tower we were going to execute an south turn thru final to lose altitude. The tower controller then cleared us for a left base and clearance to land for runway 34. We accepted that and continued to runway 34. While on the base to final turn; we realized that this approach was also not going to work as we were way too close. I then told the captain that we should go around; so I executed the go around and we made a normal visual pattern and approach to runway 2 afterwards. Cause; the fact that we were being vectored directly to the airport; at night; rather than to an approach fix was a threat. This prevented us from making an appropriate turn and developing a plan to get set up for the landing; especially since we were not cleared for the visual approach until inside of 5 miles. Additionally; we were about 45 degrees away from either of the landing runways rather than being directly lined up. Finally; realization of all of this should have happened sooner so we could have queried the controller; thus our planning was poor.
Original NASA ASRS Text
Title: Air Carrier landing RIC was vectored direct to the airport at night and cleared for a visual approach less than five miles from the airport resulting in a go around; Controller technique was listed as a causal factor.
Narrative: Approaching RIC; we were expecting the visual approach to Runway 2. We were speaking to PCT at 2;000 FT. We were given direct to the airport. I had noticed that we were 5 miles from the airport with no approach clearance. Upon reaching 4 miles from the airport; we were cleared for the visual approach to Runway 2; after calling it in sight. However; we were approaching the airport at 200 KTS and not configured for landing. After getting configured and making our own vectors; we were on a left base for Runway 2; but too close to make an approach to landing; so we told Tower we were going to execute an S turn thru final to lose altitude. The Tower Controller then cleared us for a left base and clearance to land for Runway 34. We accepted that and continued to Runway 34. While on the base to final turn; we realized that this approach was also not going to work as we were way too close. I then told the Captain that we should go around; so I executed the go around and we made a normal visual pattern and approach to Runway 2 afterwards. Cause; the fact that we were being vectored directly to the airport; at night; rather than to an approach fix was a threat. This prevented us from making an appropriate turn and developing a plan to get set up for the landing; especially since we were not cleared for the visual approach until inside of 5 miles. Additionally; we were about 45 degrees away from either of the landing runways rather than being directly lined up. Finally; realization of all of this should have happened sooner so we could have queried the Controller; thus our planning was poor.
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.