37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1365028 |
Time | |
Date | 201606 |
Local Time Of Day | 0601-1200 |
Place | |
Locale Reference | BNA.Airport |
State Reference | TN |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Make Model Name | Small Transport Low Wing 2 Turboprop Eng |
Operating Under FAR Part | Part 91 |
Flight Phase | Descent |
Route In Use | Vectors |
Flight Plan | IFR |
Person 1 | |
Function | Captain Pilot Flying |
Qualification | Flight Crew Flight Instructor Flight Crew Air Transport Pilot (ATP) Flight Crew Instrument Flight Crew Multiengine |
Experience | Flight Crew Last 90 Days 60 Flight Crew Total 3900 Flight Crew Type 250 |
Events | |
Anomaly | Deviation - Procedural Published Material / Policy |
Narrative:
During a recently planned flight to shelbyville (syi) my copilot and I saw that the runway had a NOTAM for closure after we had departed and were enroute towards syi. As we again discussed our arrival we found the NOTAM on our initial descent. Our flight ended up going to nashville anyway so it was not an issue; however the reason NOTAM was over looked was due to the way the NOTAM was presented. NOTAM was presented as follows e.g. Bna (NOTAM #) syi (NOTAM detail) on fltplan.com. Many times or at many airports notams are presented as the airport identifier e.g. Syi (NOTAM #) (NOTAM detail) and do not have a different airport in front of the affected airport. Perhaps this is the way that airport normally identifies notams. This would have been avoided had the NOTAM been presented as syi (NOTAM #) (NOTAM detail) only and not preceded by bna
Original NASA ASRS Text
Title: Corporate Captain reported that the published NOTAM was ambiguous using two airports rather than one.
Narrative: During a recently planned flight to Shelbyville (SYI) my copilot and I saw that the runway had a NOTAM for closure after we had departed and were enroute towards SYI. As we again discussed our arrival we found the NOTAM on our initial descent. Our flight ended up going to Nashville anyway so it was not an issue; however the reason NOTAM was over looked was due to the way the NOTAM was presented. NOTAM was presented as follows e.g. BNA (NOTAM #) SYI (NOTAM Detail) on fltplan.com. Many times or at many airports NOTAMs are presented as the airport identifier e.g. SYI (NOTAM #) (NOTAM Detail) and do not have a different airport in front of the affected airport. Perhaps this is the way that airport normally identifies NOTAMs. This would have been avoided had the NOTAM been presented as SYI (NOTAM #) (NOTAM Detail) only and not preceded by BNA
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.