|
|
FSFlyingSchool Training Captain
Group: Forum Members
Last Login: Monday, January 17, 2011 6:45:44 AM
Posts: 649,
Visits: 2,260
|
|
'' Hi S/L I am reposting these as I think Fenric (Stan) has raised some good points that perhaps you are best positioned to answer. Biggles | |
| Do you envision that you will issue a patch to correct the problem? ANother thought on this problem is that if you are overflying the runway to effect, say a procedure turn or go-around, the instructor has no way of knowing this and thinks that you're going to land. The ideal is to stay in cruise mode, and just switch to landing mode on short final, or a little before when you're really going in, but then you will probably be below 1000 ft in cruise mode and the instructor will be yelling at you to pull up. I'm just thinking, that maybe if this 1000' facility could be disabled, the disadvantage would be outweighed by the more realistic control of the pilot? Stan |
| Post #5687 |
|
|
|
| stanshear (11/5/2009)
Do you envision that you will issue a patch to correct the problem? ANother thought on this problem is that if you are overflying the runway to effect, say a procedure turn or go-around, the instructor has no way of knowing this and thinks that you're going to land. The ideal is to stay in cruise mode, and just switch to landing mode on short final, or a little before when you're really going in, but then you will probably be below 1000 ft in cruise mode and the instructor will be yelling at you to pull up. I'm just thinking, that maybe if this 1000' facility could be disabled, the disadvantage would be outweighed by the more realistic control of the pilot? Stan Stan I've lifted this reply from the previous post on this matter. I think the key is not being allowed below 500ft agl unless landing is the answer Any thoughts? Biggles Hi Fenric Your second point, hilighted above, is being looked at by S/L. A question though when in cruise mode & on your approach to the overhead - at what height ere you flying? I have raised the following with S/L elswhere I paste it below for info & will keep you posted re answer. Re Stans 2nd point. Agree re turning off auto landing detection but to qoute Stan . If I remain in cruise mode he'll then tell me that I can't descend whilst cruising and criticizes me for that. So what's the best way of approaching a landing according to an NDB approach chart where the FAF is very near the runway and you have to fly outbound first, do a procedure turn and then come in to land via a standard circuit because the approach is 45 deg. to the runway? If one remains in cruise mode & descends below 1000 (with auto landing off) you will get hammered for low flying!? Question is at what height do you need to descend below to trigger point deduction/debrief comment for low flying? If memory serves me right you are, in unrestricted airspace & flying FVR, not allowed to descend <500ft unless landing. Therefore I would think that this should be the point at which fsfs hits you for low flying.ie <500ft in cruise mode. This may already be the case, I don't know. If Stan has got auto landing turned off & he remains in cruise mode when inbound for the overhead on his NDB approach then, provided he doesn't descend <500ft he should not hear Smithy's criticism re If I remain in cruise mode he'll then tell me that I can't descend whilst cruising and criticizes me for that. Biggles |
| Post #5691 |
|
|
|
| OK, here's the story. I'm landing at Provincetown which has an NDB on-field. The approach chart and approach worksheet are attached. 1. You overfly the runway, and turn left 67 to be outbound in line with the runway, and reduce altitude from 3000' to 1600' over a period of about 2 mins. You should be in cruise mode at this stage to avoid Mr Smith saying something about descending, but he picks up the runway as a waypoint and starts to remind you that you need to land. He doesn't know that you intend overshooting the runway to turn back. 2. You make the left procedure turn, returning back at 202 to intersect the inbound heading at 147, descending to 1600' and turning 147 to land. At this point you need to go into descend mode and Mr Smith starts telling you that you have no glide slope. 3. When you intersect the 147 bearing you have about 2 mins to reach the NDB which is on-field. During this time you have to descend to the MDA of 500' to capture the glide slope for landing. 4. Assuming you're flying at about 75kias, you should be about 500/300 nm (using the 1/300 rule of thumb) from touchdown, namely about 1.6nm from touchdown when you reach 500'. However Mr Smith continues to admonish you about the glide slope and tells you that you're below the glide slope. Does this procedure sound right? The problem seems to be that you have no way of telling FSFS that you're firstly overflying the runway, and secondly, when you return to land, FSFS starts to sense that you're off the glideslope before the MDA. I hope I'm making sense, but this seems to be what's happening. Stan
|
| Post #5699 |
|
|
|
| stanshear (11/5/2009)
OK, here's the story. I'm landing at Provincetown which has an NDB on-field. The approach chart and approach worksheet are attached. 1. You overfly the runway, and turn left 67 to be outbound in line with the runway, and reduce altitude from 3000' to 1600' over a period of about 2 mins. You should be in cruise mode at this stage to avoid Mr Smith saying something about descending, but he picks up the runway as a waypoint and starts to remind you that you need to land. He doesn't know that you intend overshooting the runway to turn back. Strange, I would not have thought this should happen if in cruise mode Over to you S/L 2. You make the left procedure turn, returning back at 202 to intersect the inbound heading at 147, descending to 1600' and turning 147 to land. At this point you need to go into descend mode and Mr Smith starts telling you that you have no glide slope. I believe the question of Smithy bleating on about Glideslope/localiser too early has been raised & is being looked at S/L? 3. When you intersect the 147 bearing you have about 2 mins to reach the NDB which is on-field. During this time you have to descend to the MDA of 500' to capture the glide slope for landing. 4. Assuming you're flying at about 75kias, you should be about 500/300 nm (using the 1/300 rule of thumb) from touchdown, namely about 1.6nm from touchdown when you reach 500'. However Mr Smith continues to admonish you about the glide slope and tells you that you're below the glide slope. Thats one for the S/L You can alter the glideslope angle in your non ILS r/w files & see if that shuts Smithy up Does this procedure sound right? The problem seems to be that you have no way of telling FSFS that you're firstly overflying the runway, and secondly, when you return to land, FSFS starts to sense that you're off the glideslope before the MDA. I hope I'm making sense, but this seems to be what's happening. Stan Hi Fenric I think the S/L needs to answer most of this but I can see exactly what you are getting at Biggles |
|
|
|
|
|
FSFlyingSchool Developer
Group: Administrators
Last Login: Saturday, September 28, 2024 9:27:47 AM
Posts: 5,065,
Visits: 9,199
|
|
Hi guys: Thanks for all the information - this is a very interesting area and one that we are looking at. We are in the middle of a major development project at present - I will keep you posted on our ideas about the issue described in your mutual notes.
Jeff Preston ('Squadron Leader') - FSFlyingSchool Publisher & Lead Developer
FSFlyingSchool 2023 for Microsoft Flight Simulator
FSFlyingSchool 2023 for X-Plane 12 & 11
FS Instant Approach 2023 for X-Plane 12 & 11 (Windows)
FSFlyingSchool PRO 2020 Prepar3D v 5
FSFlyingSchool PRO 2019 FSX, FSX-SE, FS2004
FSFlyingSchool USA for Microsoft Flight Simulator
FS Instant Approach 2019 for X-Plane 11 (Mac)
FS Instant Approach for Microsoft Flight Simulator
FS Instant Help for FSX, FS2004
Winner of 5 consecutive PC Pilot Magazine 'Classic Product' Awards
Fly like the Pros with X-Plane, Flight Simulator and Prepar3D!
If you wish to unsubscribe simply reply to email with the word UNSUBSCRIBE in the SUBJECT line.
|
|
|
|
FSFlyingSchool Training Captain
Group: Forum Members
Last Login: Monday, January 17, 2011 6:45:44 AM
Posts: 649,
Visits: 2,260
|
|
Thanks for the quick reponse S/L It all sounds very interesting and positive. There you go Fenric, fsfs seems to move pretty fast & your issue is noted Now get back to the tour & your new scenery...........and don't forget the odd zero or two Biggles
|
|
|
|
FSFlyingSchool Training Captain
Group: Forum Members
Last Login: Thursday, September 23, 2010 9:11:34 AM
Posts: 168,
Visits: 220
|
|
Gentlemen, With all due deference and respect to Stan... I am not Stan. A. By your own definition Stan has raised ''good points.'' I have no good points to raise. B. I'm the one with a dimple in my chin. Granted, it's well hidden by my beard - but nonetheless.... C. My parents did not name me Stan. A fine name - one well worth honor and songs of legend - alas, not mine. --Fenric, not Stan
- -----
- FS2 v3.0 w/172 Detail - FSX SP2 - CH yoke & pedals - GoFlight / Saitek / MPanel - TrackIR 3 w/VE
- i7-920 airclocked to 166, Vista 64 Prem, GTX 260, 9GB 1300 DRAM, 1TB OS / 200GB s/s FSX drive
"Geronimo"
|
|
|
|
FSFlyingSchool Training Captain
Group: Forum Members
Last Login: Monday, January 17, 2011 6:45:44 AM
Posts: 649,
Visits: 2,260
|
|
Now look here Stan, don't you know it illegal to impersonate Fenric Where the heck did Stan come from ?? Don't ask me it must have been Joe Joe who? Oh heck I cant remember now My apologies to whoever I may have offended over this error, whatever your name may be Bongles
|
|
|
|
FSFlyingSchool Captain
Group: Forum Members
Last Login: Thursday, December 23, 2010 11:16:00 AM
Posts: 108,
Visits: 700
|
|
I'm Stan. My parents named me Stanley. But that shouldn't be held against me 'cos I love flightsimming and I love FSFlyingSchool.
|
|
|
|
FSFlyingSchool Developer
Group: Administrators
Last Login: Saturday, September 28, 2024 9:27:47 AM
Posts: 5,065,
Visits: 9,199
|
|
Well - I'm glad that's all sorted out!
Jeff Preston ('Squadron Leader') - FSFlyingSchool Publisher & Lead Developer
FSFlyingSchool 2023 for Microsoft Flight Simulator
FSFlyingSchool 2023 for X-Plane 12 & 11
FS Instant Approach 2023 for X-Plane 12 & 11 (Windows)
FSFlyingSchool PRO 2020 Prepar3D v 5
FSFlyingSchool PRO 2019 FSX, FSX-SE, FS2004
FSFlyingSchool USA for Microsoft Flight Simulator
FS Instant Approach 2019 for X-Plane 11 (Mac)
FS Instant Approach for Microsoft Flight Simulator
FS Instant Help for FSX, FS2004
Winner of 5 consecutive PC Pilot Magazine 'Classic Product' Awards
Fly like the Pros with X-Plane, Flight Simulator and Prepar3D!
If you wish to unsubscribe simply reply to email with the word UNSUBSCRIBE in the SUBJECT line.
|
|
|
|
FSFlyingSchool Training Captain
Group: Forum Members
Last Login: Thursday, September 23, 2010 9:11:34 AM
Posts: 168,
Visits: 220
|
|
I sensed that a group hug was about to form, so I ran and hid.
- -----
- FS2 v3.0 w/172 Detail - FSX SP2 - CH yoke & pedals - GoFlight / Saitek / MPanel - TrackIR 3 w/VE
- i7-920 airclocked to 166, Vista 64 Prem, GTX 260, 9GB 1300 DRAM, 1TB OS / 200GB s/s FSX drive
"Geronimo"
|
|
|
|
FSFlyingSchool Developer
Group: Administrators
Last Login: Saturday, September 28, 2024 9:27:47 AM
Posts: 5,065,
Visits: 9,199
|
|
HA HA HA!
Jeff Preston ('Squadron Leader') - FSFlyingSchool Publisher & Lead Developer
FSFlyingSchool 2023 for Microsoft Flight Simulator
FSFlyingSchool 2023 for X-Plane 12 & 11
FS Instant Approach 2023 for X-Plane 12 & 11 (Windows)
FSFlyingSchool PRO 2020 Prepar3D v 5
FSFlyingSchool PRO 2019 FSX, FSX-SE, FS2004
FSFlyingSchool USA for Microsoft Flight Simulator
FS Instant Approach 2019 for X-Plane 11 (Mac)
FS Instant Approach for Microsoft Flight Simulator
FS Instant Help for FSX, FS2004
Winner of 5 consecutive PC Pilot Magazine 'Classic Product' Awards
Fly like the Pros with X-Plane, Flight Simulator and Prepar3D!
If you wish to unsubscribe simply reply to email with the word UNSUBSCRIBE in the SUBJECT line.
|
|
|
|