RNAV to dirt strip
I know RNAVs are getting way more popular, but how many strips out there that are dirt/grass, have a RNAV?
|
Probably at lot more than what is published. :E
|
Originally Posted by Capt Fathom
(Post 11415675)
Probably at lot more than what is published. :E
|
It doesn’t matter the surface type, it’s got to be 139 certified to have an IAP of any type.
|
St Helens in Tassie
|
Amazed how many airstrips don’t have RNAV’s, is there a lot of work to get them approved?
Lets face it most modern GA avionics easy to build, not to mention most jet FMGC’s. Genuinely curious as to any airport that doesn’t have an approach why not? |
Originally Posted by Global Aviator
(Post 11420586)
Amazed how many airstrips don’t have RNAV’s, is there a lot of work to get them approved?
Genuinely curious as to any airport that doesn’t have an approach why not? |
Originally Posted by compressor stall
(Post 11415927)
It doesn’t matter the surface type, it’s got to be 139 certified to have an IAP of any type.
|
If you read those exemptions, there is quite the burden on the operator (and they are mainly issued to an operator) to manage the risks of unknown obstacles in those approaches.
|
The key issue is monitoring and management of obstacle limitation surfaces and IAP surfaces to protect the approach so obstacles do not appear in the approach path. System technology is not the issue. Nature and huma beings putting up obstacles are the problem.
|
As a consequence of Part 139, 4’ shrubs and 2’ too high fences have
|
If they are only that high then they are very close to the inner edges of the protected surfaces and therefore close to final approach path. It's a pity that people don't read the relevant MOS to be aware of why. The IAP and Obstacle surfaces are consistent with ICAO standards. They are not Australia specific
|
Australia complies with ICAO SARPs when it’s convenient for the Australian bureaucracy and files a difference with ICAO SARPs when … it’s convenient for the Australian bureaucracy. At least in that regard, Australian bureaucracy is consistent with other countries’ bureaucracies.
The safety consequences of drowning crew with pages of information which do not result in any practical difference to their operations? Safety shmafety. Meanwhile, for all of the pages of Part 139 and Part 175 and the dozens of strict liability offences, the system still gets a runway closure NOTAM wrong. (For those who may not be aware of the difference: A closed runway is relevant to a flight crew’s decision-making. A shrub which infringes the OLS by 4’ and a fence which infringes the OLS by 2’ are irrelevant to a flight crew’s decision-making. However, both are given the same prominence and space in the piles of information through which a flight crew is expected to wade.) |
piles of information through which a flight crew is expected to wade |
Originally Posted by megan
(Post 11421090)
... Always loved how areas referred to were given in lat/long and you're expected to plot. They've yet to realise the teletype disappeared quite some years ago, a modern invention prevails, graphics.
YMMM SIGMET J01 VALID 172300/180300 YMRF- YMMM MELBOURNE FIR SEV TURB FCST WI S4230 E14800 - S4340 E14650 - S4320 E14550 - S4150 E14520 - S4230 E14720 - S4140 E14720 - S4140 E14800 SFC/7000FT STNR NC RMK: ME= |
Graphical SIGMETS have been around for a long time, you just have to request the right stuff with your briefing. I agree, the lat/long format is well past its use by date, except for perhaps transmission over HF when pictures can't be sent.
|
Originally Posted by megan
Always loved how areas referred to were given in lat/long and you're expected to plot.
|
Thanks! I've learnt something new today.
|
I can't take the credit; I was in the crewroom a few years ago swearing and cussing about having to plot out these cursed Sigmets and a mate whispered over my shoulder "81210 is your friend". :}
|
|
All times are GMT. The time now is 19:44. |
Copyright © 2024 MH Sub I, LLC dba Internet Brands. All rights reserved. Use of this site indicates your consent to the Terms of Use.