![]() |
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
|
|||
|
|||
![]()
Don Johnstone wrote:
I am not against a technology solution per se. What I am against is looking for a solution which could take years to implement when a solution is needed tomorrow. I'm listening for that solution, but so far all I hear is more of what we are already doing: better training and pilots that don't make mistakes. Propose something (I don't have any good ideas). It seems to me that several people think that the introduction of technology will be simple, it won't. The problem is extremely complex. Ony if you think the problem is 40 gliders instead of 3 or 4, which is all that was involved in the recent collisions. Assuming that GPS is accurate enough, it isn't (especially in vertical positioning), When I overlay the GPS altitude traces from the last flight with my two GPS recorders, I see the greatest deviations (one trace compared to the other) are less than +/- 50 feet. This is less than the wingspan of my glider! Most of the time it is less than +/- 15 feet. I think this is good enough for gliders. and that it updates qickly enough, it doesn't, at least the ones we use at the moment don't, How much more often than once a second is required? That is 25 points per circle, which seems like plenty to me. Our speeds and accelerations are low, so I think an even slower rate would be adequate for thermalling and beating back and forth on a ridge. that still leaves the problem of keeping track of 40 gliders constantly changing direction realtime, can AWACS do that? Have you ever flown in a thermal with even 10 gliders? I have many times. I can not keep track of even 10 gliders, but I can still thermal safely when there are that many and more. We are not flying around at random, but circling in an orderly fashion. Only the nearby gliders are a threat that must be monitored. In any case, a system that deals with only a few gliders will cover most of the situations. Still leaves the problem of how you keep the pilot informed, display in the cockpit? I don't think so. Having sorted out all that, what does a pilot do in response to an urgent warning of collision, turn into another glider which was not logged as a threat until the sudden evasive turn was made. Technology might give the warning but it is the human that has to react. These are not new questions, so you can be assured that people contemplating these systems are considering them. Systems do not spring fully featured and perfect from the mind of an engineer, but proceed through stages of development and testing. Exactly what problems and benefits will appear during this process can't be predicted very well. I personally don't think we have the technology or expertise to design such a system or indeed the expertise to put it in a small enough space to fit in a glider right now, and the cost could be more than the average glider is worth. I am not saying do nothing, what I am saying is do something realistic and achievable now. I have little doubt that what has been proposed will be with us in 10 years time but it is now that we have a problem. I stand by what I originally wrote, humans are the cause of accidents, humans can prevent accidents. Whether we have the will to do it is another matter entirely. What must we do? Propose something - we're listening. If GPS was that accurate radar whould be obsolete GPS _IS_ far more accurate than radar! But the system that uses it is being deployed very slowly. and transponders museum items. Some of us already believe that! But I still installed one, because that is the current system best suited to keep me and airliners separated (it can also help keep smaller airplanes and even skydivers away from me). -- Change "netto" to "net" to email me directly Eric Greenwell Washington State USA |
#2
|
|||
|
|||
![]() "Eric Greenwell" wrote in message ... Don Johnstone wrote: It seems to me that several people think that the introduction of technology will be simple, it won't. The problem is extremely complex. Ony if you think the problem is 40 gliders instead of 3 or 4, which is all that was involved in the recent collisions. I'm not a programmer, but I work with them on a daily basis. It seems to me that even a 3 or 4 glider problem is highly complex because sailplanes fly in highly irregular paths. We don't even fly straight point to point--we weave left and right, we dolphin. A ship might be going (more or less) straight and a couple hundred feet below me. Not a threat, right? Maybe, maybe not--what if I'm in a thermal and he's seen me and plans to join me. He suddenly converts speed to altitude and he's in my blind spot. My GPS has a 4 second polling cycle. Ooops. What if two ships are in a thermal but maintaining separation. Everything's fine, right? Sure, until we get to the top of the lift band and he suddenly tightens his turn to go through the core as he heads out on course. Have you ever flown in a thermal with even 10 gliders? I have many times. I can not keep track of even 10 gliders, but I can still thermal safely when there are that many and more. We are not flying around at random, but circling in an orderly fashion. Only the nearby gliders are a threat that must be monitored. In any case, a system that deals with only a few gliders will cover most of the situations. Orderly? To you and I yes. To a program? Not really. Think about what happens at cloudbase in a contest gaggle. The (mostly) orderly and similar actions (mostly same speed & bank angle) get more random. Some pilots increase their radius purposefully suboptimizing climb rates, others deploy a bit of spoiler, others leave. How are these actions to be predicted? Even if I have a 1 second polling rate on my GPS & "traffic analysis/collision avoidance system", how many variables can change in that one second and how fast can my safe separation be erased? Still leaves the problem of how you keep the pilot informed, display in the cockpit? I don't think so. Having sorted out all that, what does a pilot do in response to an urgent warning of collision, turn into another glider which was not logged as a threat until the sudden evasive turn was made. Technology might give the warning but it is the human that has to react. These are not new questions, so you can be assured that people contemplating these systems are considering them. Systems do not spring fully featured and perfect from the mind of an engineer, but proceed through stages of development and testing. Exactly what problems and benefits will appear during this process can't be predicted very well. I personally don't think we have the technology or expertise to design such a system or indeed the expertise to put it in a small enough space to fit in a glider right now, and the cost could be more than the average glider is worth. I am not saying do nothing, what I am saying is do something realistic and achievable now. I have little doubt that what has been proposed will be with us in 10 years time but it is now that we have a problem. I stand by what I originally wrote, humans are the cause of accidents, humans can prevent accidents. Whether we have the will to do it is another matter entirely. What must we do? Propose something - we're listening. Here's my modest proposal, eat them. Sorry, trying again-- Don't ask the system to figure collision potential and don't introduce another screen. Just have a system call out "target NNW, same altitude, closing @ x". If I see it, I say something like "clear" or "check" and the system stops alerting me to the known target. If I don't acknowledge the target the system continues to provide information at regular intervals to help me find it. I might be re-notified of "cleared" targets if we continue to fly in proximity to one another. Frankly, I can't imagine a user interface that would be useful in a large gaggle. That's probably OK because that's where we're likely to be most alert to this type of threat. Brent |
#3
|
|||
|
|||
![]()
303pilot wrote:
"Eric Greenwell" wrote in message Ony if you think the problem is 40 gliders instead of 3 or 4, which is all that was involved in the recent collisions. I'm not a programmer, but I work with them on a daily basis. It seems to me that even a 3 or 4 glider problem is highly complex because sailplanes fly in highly irregular paths. But still more manageable the 40, right :} ? But to answer the question, and keeping in mind I don't know any details of the Flarm system, it may not be possible or necessary to have a TCAS-like system. Though several gliders flying at random may indeed be complex, the algorithms chosen can make simplifying assumptions based on the nature of glider flight. Also, the pilot arriving at a thermal might modify his arrival to keep the threat level low, compared to how he does it now, so as not to "alarm" the pilots already in the thermal (and for other situations, also, not just thermals). We don't even fly straight point to point--we weave left and right, we dolphin. A ship might be going (more or less) straight and a couple hundred feet below me. Not a threat, right? Maybe, maybe not--what if I'm in a thermal and he's seen me and plans to join me. He suddenly converts speed to altitude and he's in my blind spot. My GPS has a 4 second polling cycle. Ooops. Most GPS receivers we use emit at once a second, though _flight recorders_ might record at a slower rate (the newer ones will also record at once per second). Rate isn't a problem. What if two ships are in a thermal but maintaining separation. Everything's fine, right? Sure, until we get to the top of the lift band and he suddenly tightens his turn to go through the core as he heads out on course. This simple situation is likely easy to handle. It should cause some alarms in both cockpits, unless it is a diving exit, which would put him well below the still thermalling glider! I'm sure anyone contemplating these systems has thought of these situations and more, and intends to cope with them, and use extensive testing to validate the equipment. As I mentioned before, the equipment might cause changes in pilot behavior, perhaps because they wish to avoid causing alarms, or because they now realize better the dangers involved. Have you ever flown in a thermal with even 10 gliders? I have many times. I can not keep track of even 10 gliders, but I can still thermal safely when there are that many and more. We are not flying around at random, but circling in an orderly fashion. Only the nearby gliders are a threat that must be monitored. In any case, a system that deals with only a few gliders will cover most of the situations. Orderly? To you and I yes. To a program? Not really. Think about what happens at cloudbase in a contest gaggle. The (mostly) orderly and similar actions (mostly same speed & bank angle) get more random. Some pilots increase their radius purposefully suboptimizing climb rates, others deploy a bit of spoiler, others leave. How are these actions to be predicted? Even if I have a 1 second polling rate on my GPS & "traffic analysis/collision avoidance system", how many variables can change in that one second and how fast can my safe separation be erased? In one second? Very few. Gliders simply don't react quickly in roll, and pilots don't pitch rapidly in the cloudbase gaggle. The ones I've been in, everyone is changing direction smoothly and slowly. Away from a gaggle, pitch changes can occur rapidly, but one second still seems short enough to me. It would be better to seek the opinion of someone actually attempting this, of course! snip What must we do? Propose something - we're listening. Here's my modest proposal, eat them. Sorry, trying again-- Don't ask the system to figure collision potential and don't introduce another screen. Just have a system call out "target NNW, same altitude, closing @ x". If I see it, I say something like "clear" or "check" and the system stops alerting me to the known target. If I don't acknowledge the target the system continues to provide information at regular intervals to help me find it. If I were designing a system, I'd make this capability the first phase. Perhaps it would be good enough. I'd try a button on the stick before the confirmation. I might be re-notified of "cleared" targets if we continue to fly in proximity to one another. Frankly, I can't imagine a user interface that would be useful in a large gaggle. That's probably OK because that's where we're likely to be most alert to this type of threat. Brent -- Change "netto" to "net" to email me directly Eric Greenwell Washington State USA |
#4
|
|||
|
|||
![]()
The FLARM device not only provides traffic advisories, it tracks ground
hazards like towers and wires. It's also a IGC logger. Most handheld computers do several million floating point operations per second (MIPS) Hundreds of MIPS are available on low power CPU's. That's enough to compute trajectories on 40+ gliders in the 1/2 second interval between GPS fixes. Having enough computer power is not a problem. There are a lot of smarter people than me who could do the programming but maybe I can help with a flowchart. Step one: Are there any targets within one kilometer? If yes, provide count. Step two: Are any of these targets within + or - 200 meters of my altitude? If yes, proceed to step three. If not, ignore. Step three: For any targets within + or - 200 meters of my altitude, is the slant range increasing or decreasing? If increasing, ignore. If decreasing go to step four. Step four: For targets within +- 200 meters and closing, is the relative bearing changing less than 10 degrees per second? If yes, sound alarm and provide relative bearing and range. If greater, do nothing. Step four is a bit of oversimplification, for example, the critical rate of change for relative bearing increases for closer targets, which would require a look-up table or formula. Still, this is not a complicated algorithm. Bill Daniels "Eric Greenwell" wrote in message ... 303pilot wrote: "Eric Greenwell" wrote in message Ony if you think the problem is 40 gliders instead of 3 or 4, which is all that was involved in the recent collisions. I'm not a programmer, but I work with them on a daily basis. It seems to me that even a 3 or 4 glider problem is highly complex because sailplanes fly in highly irregular paths. But still more manageable the 40, right :} ? But to answer the question, and keeping in mind I don't know any details of the Flarm system, it may not be possible or necessary to have a TCAS-like system. Though several gliders flying at random may indeed be complex, the algorithms chosen can make simplifying assumptions based on the nature of glider flight. Also, the pilot arriving at a thermal might modify his arrival to keep the threat level low, compared to how he does it now, so as not to "alarm" the pilots already in the thermal (and for other situations, also, not just thermals). We don't even fly straight point to point--we weave left and right, we dolphin. A ship might be going (more or less) straight and a couple hundred feet below me. Not a threat, right? Maybe, maybe not--what if I'm in a thermal and he's seen me and plans to join me. He suddenly converts speed to altitude and he's in my blind spot. My GPS has a 4 second polling cycle. Ooops. Most GPS receivers we use emit at once a second, though _flight recorders_ might record at a slower rate (the newer ones will also record at once per second). Rate isn't a problem. What if two ships are in a thermal but maintaining separation. Everything's fine, right? Sure, until we get to the top of the lift band and he suddenly tightens his turn to go through the core as he heads out on course. This simple situation is likely easy to handle. It should cause some alarms in both cockpits, unless it is a diving exit, which would put him well below the still thermalling glider! I'm sure anyone contemplating these systems has thought of these situations and more, and intends to cope with them, and use extensive testing to validate the equipment. As I mentioned before, the equipment might cause changes in pilot behavior, perhaps because they wish to avoid causing alarms, or because they now realize better the dangers involved. Have you ever flown in a thermal with even 10 gliders? I have many times. I can not keep track of even 10 gliders, but I can still thermal safely when there are that many and more. We are not flying around at random, but circling in an orderly fashion. Only the nearby gliders are a threat that must be monitored. In any case, a system that deals with only a few gliders will cover most of the situations. Orderly? To you and I yes. To a program? Not really. Think about what happens at cloudbase in a contest gaggle. The (mostly) orderly and similar actions (mostly same speed & bank angle) get more random. Some pilots increase their radius purposefully suboptimizing climb rates, others deploy a bit of spoiler, others leave. How are these actions to be predicted? Even if I have a 1 second polling rate on my GPS & "traffic analysis/collision avoidance system", how many variables can change in that one second and how fast can my safe separation be erased? In one second? Very few. Gliders simply don't react quickly in roll, and pilots don't pitch rapidly in the cloudbase gaggle. The ones I've been in, everyone is changing direction smoothly and slowly. Away from a gaggle, pitch changes can occur rapidly, but one second still seems short enough to me. It would be better to seek the opinion of someone actually attempting this, of course! snip What must we do? Propose something - we're listening. Here's my modest proposal, eat them. Sorry, trying again-- Don't ask the system to figure collision potential and don't introduce another screen. Just have a system call out "target NNW, same altitude, closing @ x". If I see it, I say something like "clear" or "check" and the system stops alerting me to the known target. If I don't acknowledge the target the system continues to provide information at regular intervals to help me find it. If I were designing a system, I'd make this capability the first phase. Perhaps it would be good enough. I'd try a button on the stick before the confirmation. I might be re-notified of "cleared" targets if we continue to fly in proximity to one another. Frankly, I can't imagine a user interface that would be useful in a large gaggle. That's probably OK because that's where we're likely to be most alert to this type of threat. Brent -- Change "netto" to "net" to email me directly Eric Greenwell Washington State USA |
#5
|
|||
|
|||
![]()
Bill Daniels wrote:
The FLARM device not only provides traffic advisories, it tracks ground hazards like towers and wires. It's also a IGC logger. AFAIK it is not _yet_ an IGC logger. At the moment, the developers concentrate on collision avoidance, IGC logger approval is secondary priority. Friday there'll be another meeting/presentation here at Zuerich with news, updates and discussions. FLARM does NOT provide to the pilot a count of targets in a certain vicinity. A count is a minor factor for collision avoidance and can easily lead to confusion (remember that only FLARM equipped A/C can be targetted!). -Gerhard |
Thread Tools | |
Display Modes | |
|
|
![]() |
||||
Thread | Thread Starter | Forum | Replies | Last Post |
For Keith Willshaw... | robert arndt | Military Aviation | 253 | July 6th 04 05:18 AM |
Anti collision lights mods for Arrow 1968?? | Frode Berg | Piloting | 3 | May 20th 04 05:42 AM |
Anti collision light mod for Piper Arrow 1968 model? | Frode Berg | Owning | 4 | May 20th 04 05:16 AM |
New anti collision system for aircrafts, helicopters and gliders | Thierry | Owning | 10 | February 14th 04 08:36 AM |
USAF = US Amphetamine Fools | RT | Military Aviation | 104 | September 25th 03 03:17 PM |