My dad has a Bonanza and loves your app. Here is a suggestion for a new feature. The app knows the length of the runway, the takeoff speed calculated with temperature and altitude, acceleration, braking power, and GPS position. It should be possible to calculate a go/no go warning with a suitable margin of safety. I can do the calculations, but don't have experience developing/publishing apps.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
That’s a very interesting suggestion. The app may or may not have the current METAR and therefore may not know the expected ground roll and the expected ground speed at Vr. If it had the current METAR it could predict the expected speeds at different points in the ground roll by making some simplifying assumptions (constant acceleration).
Currently, the app does not know the device’s GPS location. The app knows the GPS coordinates of the airport (roughly the “center” of the airport) but it doesn’t know the GPS coordinates of the runway ends. The global airport database that the app uses (ourairports.com) does not always publish this information. All this would require substantial work.
Lastly, there’s a liability issue. The app currently only presents POH data. It is not responsible for the data itself. This would put the app directly in a safety critical situation and will need to be reviewed by lawyers.
Steve Kleiman
POH Performance LLC
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
My dad has a Bonanza and loves your app. Here is a suggestion for a new feature. The app knows the length of the runway, the takeoff speed calculated with temperature and altitude, acceleration, braking power, and GPS position. It should be possible to calculate a go/no go warning with a suitable margin of safety. I can do the calculations, but don't have experience developing/publishing apps.
Amanda,
That’s a very interesting suggestion. The app may or may not have the current METAR and therefore may not know the expected ground roll and the expected ground speed at Vr. If it had the current METAR it could predict the expected speeds at different points in the ground roll by making some simplifying assumptions (constant acceleration).
Currently, the app does not know the device’s GPS location. The app knows the GPS coordinates of the airport (roughly the “center” of the airport) but it doesn’t know the GPS coordinates of the runway ends. The global airport database that the app uses (ourairports.com) does not always publish this information. All this would require substantial work.
Lastly, there’s a liability issue. The app currently only presents POH data. It is not responsible for the data itself. This would put the app directly in a safety critical situation and will need to be reviewed by lawyers.
Steve Kleiman
POH Performance LLC