 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Lancair pilot reported lack of necessary airport information available from metar via ads-B on efb applications.
| Attributes | |
| ACN | 1683237 |
| Time | |
| Date | 201909 |
| Local Time Of Day | 0601-1200 |
| Place | |
| Locale Reference | CDN.Airport |
| State Reference | SC |
| Environment | |
| Flight Conditions | VMC |
| Light | Daylight |
| Aircraft 1 | |
| Make Model Name | Lancair Evolution |
| Operating Under FAR Part | Part 91 |
| Flight Phase | Final Approach |
| Flight Plan | None |
| Person 1 | |
| Function | Single Pilot |
| Qualification | Flight Crew Instrument Flight Crew Private |
| Experience | Flight Crew Last 90 Days 15 Flight Crew Total 3000 Flight Crew Type 500 |
| Events | |
| Anomaly | Aircraft Equipment Problem Less Severe Conflict Ground Conflict Less Severe Deviation - Procedural Published Material / Policy Ground Incursion Runway |
Narrative:
Flying a practice instrument approach to cdn to a miss. Fine. But on short final: whoops! Construction equipment all over the runway! No safety threat from the (planned) miss; but maybe a little scare for the workers? We get all our data from the ads-b system these days; not phone calls to flight service.we need the metar system to broadcast any airport or runway closures as part of the metar format; in a way that foreflight; garmin pilot; flyq; xavion; and the and all the other efb applications can interpret! We are using these applications to get our data; and if mine had said 'runway closed!' or 'airport closed!'; then this possibly-uncomfortable situation could have been avoided. See we need the metar data to broadcast airport/runway closure via the ads-B system to the applications so we can get this info where we are really looking for it. I wrote xavion and would surely do my part to code display of this info in my application if the info was available!
Original NASA ASRS Text
Title: Lancair pilot reported lack of necessary airport information available from METAR via ADS-B on EFB applications.
Narrative: Flying a practice instrument approach to CDN to a miss. Fine. But on short final: Whoops! Construction equipment all over the runway! No safety threat from the (planned) miss; but maybe a little scare for the workers? We get all our data from the ADS-b system these days; not phone calls to Flight Service.We need the METAR system to broadcast any airport or runway closures as part of the METAR format; in a way that ForeFlight; Garmin Pilot; FLYQ; Xavion; and the and all the other EFB applications can interpret! We are using these applications to get our data; and if mine had said 'runway closed!' or 'airport closed!'; then this possibly-uncomfortable situation could have been avoided. See we need the METAR data to broadcast airport/runway closure via the ADS-B system to the applications so we can get this info where we are really looking for it. I wrote Xavion and would surely do my part to code display of this info in my application if the info was available!
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.