Jump to content

Schlapperklange

Members
  • Posts

    32
  • Joined

  • Last visited

Everything posted by Schlapperklange

  1. Some other previews. I gave it a civil registration - N203AJ
  2. My first try to paint the Bronco. It's fictious, just an idea:
  3. Thanx for the hint. I accidently swapped the SID names. That happens if you don't have time to review your work.
  4. I will fix the errors in the next release. 1. I will correct the spelling error 2. I will add a minimum initial climb on the KPT 2 W SID of 1000 ft/min until 3.0 DME ANF to keep clear of the hill. 3. The R097 KPT on the KPT 2 E should be changed to R096 to minimize possibility of overshooting. It works well if you keep strictly the speed limit, but with strong wind from south you may overshoot easily. 4. I am thinking about adding a SID via INN NDB. Something simple like: On RWY track after 11.0 DME ANF RT direct INN NDB. Did someone else experience problems with the ANF VOR tuning? There is a DME at EDDM which also uses 115.00 Mhz. Maybe the Andras Field developers should change the frequency in the next release to eliminate possible interferences.
  5. Here is a new set of charts. Now added the SID chart and formatted them all into A4 PDF files correctly. EAFS_ILS_09.pdf EAFS_ILS_27.pdf EAFS_STAR_ALL.pdf EAFS_SID_ALL.pdf I hope you enjoy!
  6. Of course it is possible to fly the SID Rwy 27 with an arrival AT 7000 ot above - if your aircraft has enough climb capability. For most it should be no problem. Maybe we should just assume that this SID is no problem. SID Rwy 09 is no problem at all. Arrivals should be already AT 5000 when passing/holding at KPT VOR (if not other directed by ATC). Maybe I should fortify that in the remarks in the STAR chart. I intentionally don't want to use other navaids. Andras is a small airfield. So we should keep IFR proceedures short. And an insertion of custom waypoints brings new problems. Just look at the problem how to add Andras Field to the AIRAC databases.
  7. My question is: Must there be a Maltese cross at the FAF on the chart or not? Most airports' FAF have a RNAV fix with coordinates and a name. The problem is, that departing aircraft must arrive at ANF VOR higher than 5000 ft to not get into conflict with arriving traffic that arrive at 5000 ft. So a hold at ANF doen't solve the problem. If we have to add a hold for climbing, it must be before ANF, for example like this:
  8. Well, the charts are still in beta. You are right about the FAF, but actually there is no real FIX. So I am not sure if I should add a cross to the chart or not. For first I decided not to. I should delete the crosses over the ANF NDB also. It would be great if Aerosoft would create two real Approach Fixes in future releases and give it a name. And yes, the Decision Heights are quite high. For ILS 09 this was fully intended, because there is a small hill on approach, that could get dangerous if too low on approach. For ILS 27 I just copied the heights. If you can give me some better, more realistic values, I will change it. Here is an Idea about the SIDs: I don't want collide with other procedures of other airports around Andras Field, so I keep it close to the airfield. And there is only KPT VOR in vicinity. But the problem is, that KPT VOR is very close when flying the SID for RWY 27: You need tough climb rates to be at or above 7000 ft before KPT VOR. 7000 ft because if you go lower, you will have a conflict with arriving traffic. Still missing some numbers. I have only few time to do some test flights.
  9. Here is an overworked STAR - now there should be no conflict between Aircraft on ILS RWY 27 approach and those on KOGOL arrival. EAFS_STAR_ALL.pdf
  10. Ok, I am back. Any Ideas about the SID routings?
  11. Your idea is good and I know it seems a little unorthodox to make a detour for an approach on rwy 27 via KPT. But most customers of Andras Field will fly with small aircraft of which many may not be able to fly RNAV or GPS approaches. My idea was to fly the ILS approach by radio navigation only. So all ILS/VOR-DME equipped aircraft can use it. The STAR was made additionally for those who navigate with FMC/GPS until reaching IAF (KPT). In my opinion this is suffient for a small airfield like Andras. And there is another reason: The fixes you suggested to use are enroute intersections. I am not sure if it is usual to use them as approach fixes. Trondheim has it's own approach related fixes. If there would be a better positioned VOR (like the former EUR VOR) I would be happy. But I want stick to the active NAV points. This is important if we want use Andras Field on networks like IVAO or VATSIM one time (I hope so).
  12. What do you think about this STAR? EAFS_STAR_ALL.pdf
  13. I can't find EUR VOR, but I wouldn't use MAH VOR for an approach. There would be a conflict: MAH is used for EDDM ILS 08R approach, besides it is quite far away. I am thinking about a STAR via MERSI, KOGOL and BODAN that all end at KPT VOR. If you fly only VOR to VOR, I recommend also you start approach at KPT VOR. This would change if we would have another usable VOR in close east of EAFS, but there is not.
  14. Please keep in mind these are not final releases!
  15. Here a new preview of the ILS 09 & 27 charts with some fixed errors. EAFS_ILS_Charts.pdf
  16. Ok, I give you an example, here for Frankfurt (EDDF) ILS CAT II & III or LOC for RWY 07R: You can see here that the approches begin related to RID or TAU VOR until turning to intercept the ILS. Then DME is related to FRD, which is just a DME, nor an ILS neither a VOR. I did it in a similar way in my chart. Maybe in UK it is different. But the reason why I refer to a german DFS chart is clear: Andras Field lies in german airspace. If you have difficulties to fly the approach try to do it as followed: Use NAV 1 to fly on 135° radial from KPT and tune ANF on NAV 2. At 7.0 DME KPT turn left HDG 115, tune AFK on NAV 1 and intercept the ILS. Switch DME to read NAV 2. Intercept G/S at 5.6 DME ANF.
  17. I don't know the Navigraph charts. I also don't know APK. I think you mean AFK, the ILS. Take a look the the DFS charts and you will find out, that all DME related numbers are never related to an "ILS-DME". If the ILS is not working, you need another DME for your approach. This may be a VOR-DME or a stand-alone DME. If you saw something different, please tell me for what airport so I can check it out. But there is an error in the profile: I forgot to change the 7.5 DME KPT to 7.0 DME KPT. It will be corrected in the final release, in which I will add a chart for ILS RWY 27 and maybe STAR and SID charts - but after my vacation ... expect 5 weeks minimum
  18. Thanks, got it. Here is the final release candidate: EAFS_ILS_09.pdf Alex
  19. Here is a pic that shows the the position (calculated 6.8 DME ANF) on that you would intercept G/S on a 4.0° approach. It seems possible, but over the hill you might come below OCA of 444 ft. And LOC-DME should be prohibited! I my opinion it is too dangerous.
  20. I didn't see your post. I entered an OCA of 450 for all classes. But I will adopt your suggestions and change the chart - it seems to be more realistic. Also I delete classes D and E. They shouldn't operate from Andras Field at all.
  21. Yes, the coordinates would be nice to know. And I need some help on the OCA (OCH) and Timing entries. Alex
  22. New update: The chart should be useble now. Maybe someone can do some test-flights and report experience and report errors or make suggestions for improvements?
×
×
  • Create New...