Greenie Board Possibilities?

[Paddles]

Well, guys,
here's another WIP update. The project has changed drastically - no more that huge red frames mess.  Now it implements an idea found in OUTER-LOOP CONTROL FACTORS FOR CARRIER AIRCRAFT, Robert K. Heffley, 1 December 1990 (see http://www.fsdreamteam.com/forum/index.php?topic=4138.msg37985#msg37985, thank Spaz again).

..a boundary can be computed which represents the locus of points in the vertical plane from which the aircraft will reach an on-glideslope condition at the ramp (OK GS and OK rate-of-descent). This allows for the LSO to make a final judgement of the approach and for the aircraft to continue on a trajectory to the desired arresting wire. (see the attached figure). The same (rather 'scientific') approach is now used in the program to judge a landing attempt and to timely waveoff a bad one.

The user interface has changed a bit too, and will be changed more, I guess. For example, I'd like to add a separate window with the debriefing text and a final approach trajectory, plotted over the GS geometry. This would help a pilot to find his errors and see bad trends and so on...

If time permits, we'll be able to start alpha- and beta-testing in a couple of weeks or so [fingers crossing]   

[SpazSinbad]

fsxnp, I'm no 'lateral thinker'.  Would never have thought to have used that excellent PDF and ideas how you have. Well done. Looks impressive.

Question: Can the same 'approach' be used in a new version of FCLP missions? Something for the far future for sure. 

[Paddles]

Yep, it will definitely be used for the FCLP missions. And this future is not that far 

[GOONIE]

Oh my god Serge!  This is looking really sweet!!!

Can't wait for the alpha and bravo tests, thanks for all your hard work on the vLSO tool, it is really going to add a lot of fun and realism to carrier traps and FCLP landing practice.

-Capt

[GOONIE]

Also, what aircraft is in the vLSO GUI? Looks like an F-35???

By the way I really like the format and content of the GUI.

-Capt

[Sludge]

Serge...

Cheeze and Rice, you are going completely ABOVE and BEYOND on this.  Your work is looking amazing!!  Again, whatever time you have to take... so be it, but I'm really fired up to do this.  Especially with all the upgrades done for the S/C v1.2 CHARLIE, I cannot wait to fly carrier patterns with your mission.

Later
Sludge

[wilycoyote4]

Very interesting
Amazing, keep at it.

[SpazSinbad]

capthaltli asks: "Also, what aircraft is in the vLSO GUI? Looks like an F-35???" That is an excellent photo. Square intake makes it a Super Hornet of some kind. Here is a link [first] for the GUI pic plus with a story (for the second pic [similar] with caption + explanation): [So far only the X-35C has done FCLP (some 200+ times) whilst the first F-35Cs are not scheduled to go to sea until 2013 AFAIK.]

http://upload.wikimedia.org/wikipedia/commons/d/d8/FD_LSO_CVN-75_15Jan2007.jpg

“Lex:– I’ve been a big fan of your site for a while. I’m CAG Paddles on the Ronnie Reagan and was on the platform for this shot (in the back with the headset on) which was taken a couple of days ago. I had no idea that the picture was taken and was very surprised to see it on your site. Our “wave” Teams today consist of a Paddles from each squadron–usually about five guys. There is the Controlling LSO, Backup, CAG Paddles, writer, deck caller, and also a timer for groove length and interval between aircraft. Of course, there is the enlisted hook spotter, gear cross-checker, and lens rep. (all with cranials on). Obviously, it makes for a crowded platform but is necessary for safe operations today. Yes, we are looking back at a Hornet which just trapped. And yes, we are girly-men for the wind screen! Thanks and keep up the good work. Taco”

http://www.neptunuslex.com/2008/03/26/motivating-naval-aviation/

ORIGINAL HI-REZ: [for pic below]
http://www.navy.mil/management/photodb/photos/080324-N-3659B-190.jpg

[Paddles]

Also, what aircraft is in the vLSO GUI? 

I believe it's a Super Hornet. 

Well, as I mentioned earlier, I've added a separate debrifieng window. However, there's currently only an approach image, textual debriefing is still to come. The attached are a couple of my test approaches 'debriefed'. The three colored areas show the glideslope deviations, from 0.3 (green), to 0.8 (yellow) and to 1.3/1.6 (red). How do you find this way of presentation? Any suggestions/criticism/whatever are welcome.

[SpazSinbad]

fsxnp, you will have the real LSOs asking about your stuff soon. I bet they would like to be able to show this graph during their debriefs. With all their high tech today I wonder why it is not possible?

It is too early in the morning for me to understand what you mean by the decimal numbers you mention. However if possible it would be great to see a 'graph' of horizontal/vertical lines with numbers in feet for height and yards for distance (Nautical Mile being measurement) perhaps in a decimal form (or even feet but this is less helpful probably). The lines can be discrete, less obvious but will help gauge the actual deviation represented by the actual approach red line. This is a whole new way of thinking about the approach for sure.

[SpazSinbad]

Latest LSO June 2011 has some info about updates to their equipment which may give 'fsxnp' some ideas perhaps. I'm not quite sure myself what current LSO stuff does onboard but it seems that they may want what fsxnp will be delivering for FSX!

Page 5 & 6 are shown/attached below from: http://www.hrana.org/documents/PaddlesMonthlyJune2011.pdf  (1.6Mb)

[Paddles]

Spaz,
thanks for this really good info. The new iPARTS screenshots look nice.
Down to the vLSO debriefing window... I have changed its apperance a bit. Now you can see both the areas names and their distances, as well as the glideslope deviations with their LSO notations. I intentionally do not use any altitude readouts, because in case of FCLP, even flying level, your altitude will vary significantly, as shown on the last picture. So I thought it would be better to show only deviations. 

[SpazSinbad]

My expectation about the graph would be to have the altitude in a faint line, to be read as required. But maybe that is just me.

About altitude. Nothing wrong with having AGL where for FCLP it is the given runway altitude (which may vary slightly on an up/down runway so you could use the touchdown point as the datum). Also the carrier deck height is known so that could be subtracted from ASL to give the 'AGL'. Just a thought. In my view having the altitude comparing 'in close' to 'at the start' one can more easily gauge the magnitude of needed correction. Still in all the chart is excellent and your concepts seem 'on the money'.

[GOONIE]

  whoa I was way off on the aircraft, granted I wasn't working with much, just one landing strut, but in the picture Spaz posted, you can clearly see it is a rhino with the jet intake. At least I didn't guess the X-47 UCAV  

Serge, I like the altitude/glide slope deviation for debrief. One thing would be to make the debrief screen seem more military like, simple colors, like black background, with white path (red and green deviations), kinda like the iPARTS God's eye view of the carrier pattern in Spaz's post. Just a cosmetic thing, not sure if you agree.

[SpazSinbad]

In this FOV (Field of View) illustration we can see how the deck height is taken into account perhaps? From: http://www.robertheffley.com/docs/HQs/NAVAIR_2002_71.pdf