 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
A communications breakdown between the pilot and ATC resulted in a descent to a lower altitude that triggered an ATC low altitude alert.
| Attributes | |
| ACN | 981059 |
| Time | |
| Date | 201111 |
| Local Time Of Day | 1201-1800 |
| Place | |
| Locale Reference | BNA.Airport |
| State Reference | TN |
| Environment | |
| Light | Dusk |
| Aircraft 1 | |
| Make Model Name | Small Aircraft Low Wing 1 Eng Fixed Gear |
| Operating Under FAR Part | Part 135 |
| Flight Phase | Initial Approach |
| Route In Use | Vectors |
| Flight Plan | IFR |
| Person 1 | |
| Function | Single Pilot |
| Qualification | Flight Crew Commercial Flight Crew Flight Instructor Flight Crew Instrument Flight Crew Multiengine |
| Experience | Flight Crew Last 90 Days 60 Flight Crew Total 2300 Flight Crew Type 1000 |
| Events | |
| Anomaly | ATC Issue All Types Deviation - Altitude Overshoot Deviation - Procedural Clearance Inflight Event / Encounter CFTT / CFIT |
Narrative:
On ILS 2C at bna; I was being vectored to the localizer. Well prior to intercept; I was reassigned the ILS for 2R. I was given descent instructions and vectors to allow for faster traffic. I remember being given instructions to turn heading 020 and descent and maintain 2;000. This could be in error but this is what I recall. I questioned the heading only; as it didn't make sense (parallel to the localizer course but several miles east of it); but didn't question the altitude; and read back 2;000. Upon reaching 2;300 ft; I received a low altitude alert; and I was instructed to climb and maintain 3;000. Non-rated passenger stated immediately after this call that he also heard the controller assign me 2;000. No egpws terrain warning was triggered.in hindsight; I should have recognized that 2;000 was too low for both approaches; whether this was assigned by the controller in error; or I readback the wrong altitude. I did note that the published gsia for ILS 2C was 2;500. However; I had not fully briefed ILS 2R given the unexpected switch and unusual vectors. Frequency was very congested; and it sounded like 2 controllers; one overriding the other.
Original NASA ASRS Text
Title: A communications breakdown between the pilot and ATC resulted in a descent to a lower altitude that triggered an ATC low altitude alert.
Narrative: On ILS 2C at BNA; I was being vectored to the localizer. Well prior to intercept; I was reassigned the ILS for 2R. I was given descent instructions and vectors to allow for faster traffic. I remember being given instructions to turn heading 020 and descent and maintain 2;000. This could be in error but this is what I recall. I questioned the heading only; as it didn't make sense (parallel to the localizer course but several miles east of it); but didn't question the altitude; and read back 2;000. Upon reaching 2;300 FT; I received a low altitude alert; and I was instructed to climb and maintain 3;000. Non-rated passenger stated immediately after this call that he also heard the controller assign me 2;000. No EGPWS terrain warning was triggered.In hindsight; I should have recognized that 2;000 was too low for both approaches; whether this was assigned by the controller in error; or I readback the wrong altitude. I did note that the published GSIA for ILS 2C was 2;500. However; I had not fully briefed ILS 2R given the unexpected switch and unusual vectors. Frequency was very congested; and it sounded like 2 controllers; one overriding the other.
Data retrieved from NASA's ASRS site as of April 2012 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.