![]() |
If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
|
Thread Tools | Display Modes |
|
#1
|
|||
|
|||
![]()
At 16:53 31 October 2012, Ramy wrote:
Don, the statement said " can not see the one which will hit them" not the = one which hit them! You misunderstood again. What the statement means is t= hat your eye can barely detect non moving target, and the non moving target= is the one which will hit you. I suggest you do some research before posti= ng more BS.=20 Ramy Yes Ramy I do understand that. FLARM was originally designed to alert pilots flying in wave, where the relative movement of soaring gliders is very small, and their direction of travel, (track) is often unrelated to their heading (direction they are pointing) to an outside observer. FLARM is very good at alerting us of that situation and quite often the rate of closure is very small. That is just one situation where FLARM is excellent however it does not necessarily mean that it is good in other situations. |
#2
|
|||
|
|||
![]()
Don, can you back up your claim that Flarm was designed mainly for wave flying by providing some reference?
Also,can you share with us your actual experience flying with Flarm? Ramy |
#3
|
|||
|
|||
![]()
At 02:05 01 November 2012, Ramy wrote:
Don, can you back up your claim that Flarm was designed mainly for wave flying by providing some reference? Also,can you share with us your actual experience flying with Flarm? Ramy The original FLARM was conceived to assist pilots in detecting difficult to see gliders, particulary in wave where the relative movement is small, the closure rate is slow and the track of another glider cannot easily be detected by observing the way it is pointing. I fly a Discus fitted with FLARM and an LX8000. The LX8000 linked to the FLARM provides a "radar" display on the moving map. I have found the system to be useful when flying in wave, I have found it to be less useful, if not distracting in thermals. On a short 3 mile ridge with 20 or 30 gliders it is positively lethal. I do not use the LX8000 display at all when flying a ridge or in thermals. I have used it when flying in wave, however I still feel the time spent looking at the LX display and trying to make sense of it would be better spent looking out. The most scary thing, even using just the clock lights on the basic system, is that it is misleading when flying a ridge in higher wind speeds. The light bears no relation to the direction of the threat so I hear the bleep and look all round. I have to say that there have been very few occasions when the alert has sounded and I have not seen the glider causing it before the alert sounded, lucky maybe? |
#4
|
|||
|
|||
![]()
On Thursday, November 1, 2012 5:45:02 AM UTC-7, Don Johnstone wrote:
At 02:05 01 November 2012, Ramy wrote: Don, can you back up your claim that Flarm was designed mainly for wave flying by providing some reference? Also,can you share with us your actual experience flying with Flarm? Ramy The original FLARM was conceived to assist pilots in detecting difficult to see gliders, particulary in wave where the relative movement is small, the closure rate is slow and the track of another glider cannot easily be detected by observing the way it is pointing. I fly a Discus fitted with FLARM and an LX8000. The LX8000 linked to the FLARM provides a "radar" display on the moving map. I have found the system to be useful when flying in wave, I have found it to be less useful, if not distracting in thermals. On a short 3 mile ridge with 20 or 30 gliders it is positively lethal. I do not use the LX8000 display at all when flying a ridge or in thermals.. I have used it when flying in wave, however I still feel the time spent looking at the LX display and trying to make sense of it would be better spent looking out. The most scary thing, even using just the clock lights on the basic system, is that it is misleading when flying a ridge in higher wind speeds. The light bears no relation to the direction of the threat so I hear the bleep and look all round. I have to say that there have been very few occasions when the alert has sounded and I have not seen the glider causing it before the alert sounded, lucky maybe? Lucky, yes. In a dozen flights I probably picked up 10-15 conflicts that I had not already determined to be a threat visually. Examples include: an LS-8 doing a zoomie from down below my nose after overtaking me from behind/below, a Discus 2 that decided to leave a thermal by cutting through the middle of the circle and across my path from above/behind, a glider a half mile abeam of me that changed to a converging course line. On top of that there were multiple cases of traffic encountered on course and gliders adjusting their circles in thermals, I found most of them immediately useful and a couple were downright sobering. I never use the radar display in a thermal - it's not good for that and not intended for that, but it is useful in making you aware when a glider you might not have seen is now in your general vicinity. Mis-using the radar display by going heads-down in close quarters is not grounds for a sweeping criticism of the device. You could make the same criticism of an airspeed indicator - staring at it until you fly into an obstacle would be dangerous and dumb, but isn't a reason to remove the instrument from your panel. I recall the same as UH - that Flarm was developed for Alpine flying, but not especially for wave - (which is a small portion of overall flight time). I always understood Flarm was targeted at a general set of glider collision threat scenarios - all of which would be exacerbated by the traffic funneling that mountain flying of every form tends to generate. I expect Urs could clarify. 9B |
#5
|
|||
|
|||
![]()
I have had most conflicts when flying under cloud streets, including one incident a couple of years ago where I nearly collided head-on with a colleague at very high closing speeds. My concern with PowerFlarm and its cheesy antennas is that the range may not be sufficient to adequately warn me in this scenario. The more information the unit can provide the better - that is why I oppose use of the"stealth" mode.
Mike |
#6
|
|||
|
|||
![]()
On Nov 1, 9:23*am, Mike the Strike wrote:
I have had most conflicts when flying under cloud streets, including one incident a couple of years ago where I nearly collided head-on with a colleague at very high closing speeds. *My concern with PowerFlarm and its cheesy antennas *is that the range may not be sufficient to adequately warn me in this scenario. *The more information the unit can provide the better - that is why I oppose use of *the"stealth" mode. Mike Mike, I had exactly that scenario at Parowan during the nationals this year. Was near cloudbase at about 17,000 feet and doing over 100 knots indicated or about 120 mph over the ground. Light angle was low as I was running back to the southwest and the air noise from flying fast made it hard to hear the Flarm. My Butterfly display switched to conflict mode and showed a target straight ahead and at my altitude. I banked immediately and dove in time to watch W3 pass me in the opposite direction at about the same speed. Closing speed was around 240 mph (390 kmh), this would have worked in stealth mode so I have no problems recommending stealth mode for contests. Tim (TT) |
#7
|
|||
|
|||
![]()
On Thursday, November 1, 2012 8:48:01 AM UTC-7, Tim Taylor wrote:
On Nov 1, 9:23*am, Mike the Strike wrote: I have had most conflicts when flying under cloud streets, including one incident a couple of years ago where I nearly collided head-on with a colleague at very high closing speeds. *My concern with PowerFlarm and its cheesy antennas *is that the range may not be sufficient to adequately warn me in this scenario. *The more information the unit can provide the better - that is why I oppose use of *the"stealth" mode. Mike Mike, I had exactly that scenario at Parowan during the nationals this year. Was near cloudbase at about 17,000 feet and doing over 100 knots indicated or about 120 mph over the ground. Light angle was low as I was running back to the southwest and the air noise from flying fast made it hard to hear the Flarm. My Butterfly display switched to conflict mode and showed a target straight ahead and at my altitude. I banked immediately and dove in time to watch W3 pass me in the opposite direction at about the same speed. Closing speed was around 240 mph (390 kmh), this would have worked in stealth mode so I have no problems recommending stealth mode for contests. Tim (TT) Tim, I would have seen the target apporximately 4 mile out on my Ultimate Le Display, and then the Lady would warn me of the traffic, so I do not recommend the Stealth Mode. More time to identify the threat is much better. Richard www.craggyaero.com |
#8
|
|||
|
|||
![]()
At 15:23 01 November 2012, Mike the Strike wrote:
I have had most conflicts when flying under cloud streets, including one in= cident a couple of years ago where I nearly collided head- on with a colleag= ue at very high closing speeds. My concern with PowerFlarm and its cheesy = antennas is that the range may not be sufficient to adequately warn me in = this scenario. The more information the unit can provide the better - that= is why I oppose use of the"stealth" mode. Mike Mike, This link to an illustration of glider sizes versus time to impact and speeds might offer reassurance about sufficiency of warning in the head on case - assuming that the PF range collision alert range is at least as good as the less powerful Swiss Flarm version. For example, with both gliders doing 108 knots towards each other on a collision course, the first PF alert would be at around 2km separation and at that distance a 15m wingspan will subtend an angle smaller than a screw head on the instrument panel. http://www.flarm.com/files/glider_shapes_en.pdf John Galloway |
#9
|
|||
|
|||
![]()
I have had most conflicts when flying under cloud streets, including one incident a couple of years ago where I nearly collided head-on with a colleague at very high closing speeds. My concern with PowerFlarm and its cheesy antennas is that the range may not be sufficient to adequately warn me in this scenario. The more information the unit can provide the better - that is why I oppose use of the"stealth" mode.
Mike, we all know the history we had with poor range beginning of this season. But I do think we have that under control now. If you still find 'cheesy' installations, feel free to invite the responsible operators to improve them in everybody's interest. Luckily, there's a correlation between the reception characteristics of most installations and the conflict situation with highest approach speed (head-on)--- most antennas are in the nose and radiate best in front of the glider. For parallel course, you don't need 10NM range because the potential closing speeds are much lower. We recommend not activating stealth! Best --Gerhard |
#10
|
|||
|
|||
![]()
On Nov 2, 4:23*am, wrote:
We recommend not activating stealth! Best --Gerhard Presuming that the systems and installations in use have been well tested in open mode for adequate range in all directions in open mode: why not? I really only want one thing from flarm: anti-collision warning. Tracking "bugs" across a small cockpit display and trying to make tactical decisions based on same is simply not a game I am interested in playing. Evan Ludeman / T8 |
|
Thread Tools | |
Display Modes | |
|
|
![]() |
||||
Thread | Thread Starter | Forum | Replies | Last Post |
Logger on PowerFlarm? | LOV2AV8 | Soaring | 7 | July 27th 12 03:18 AM |
PowerFLARM Brick and PowerFLARM Remote Display Manuals Available | Paul Remde | Soaring | 30 | May 25th 12 11:58 PM |
PowerFLARM | Paul Remde | Soaring | 9 | November 6th 10 04:30 AM |
PowerFLARM | Greg Arnold[_2_] | Soaring | 6 | November 2nd 10 09:32 AM |
PENTAGON CONSIDERING MILITARY BUILD UP AGAINST IRAN (Scroll down to comments section - see page 2 of the comments section as well): | [email protected] | Naval Aviation | 0 | December 19th 06 08:37 PM |