My first military flightplans

[Joseph29]

Tonight I took a stab at making new plans for the JYAI RAF Shadow R1 aircraft. I have done a few general aviation plans before but never military plans.

I was hoping someone can please look them over for me and make suggestions on how to improve on them and find any errors (I don't think there are errors). Thank you very much.


Here are the plans

AC#1,G-LBSB,1%,WEEK,IFR,0/10:23:51,0/11:32:45,150,R,0000,EGXW,0/13:59:11,0/14:13:57,150,R,0000,EGXW,1/09:19:31,1/10:03:39,300,R,0000,EGOV,2/14:10:47,2/15:31:55,300,R,0000,EGXW,3/09:11:26,3/10:06:34,350,R,0000,EGPK,3/15:26:47,3/16:21:18,350,R,0000,EGXW,4/09:00:00,4/11:19:03,150,R,0000,EGXW,5/09:23:02,5/09:50:24,200,R,0000,EGUN,5/12:15:18,5/13:06:36,350,R,0000,EGNT,5/13:48:49,5/14:27:07,220,R,0000,EGXW,6/09:14:04,6/10:22:58,150,R,0000,EGXW

AC#2,ZZ416,1%,WEEK,IFR,0/09:11:15,0/09:49:11,300,R,0000,EGXW,0/12:56:26,0/13:23:22,100,R,0000,EGXW,1/14:20:59,TNG1/15:22:30,100,R,0000,EGXW,2/09:19:10,2/10:04:38,350,R,0000,EGDY,2/12:24:58,2/13:09:24,350,R,0000,EGXC,2/15:44:18,2/16:02:00,200,R,0000,EGXW,3/09:32:21,3/11:37:24,100,R,0000,EGXW,4/11:58:25,4/12:36:16,300,R,0000,EGLF

AC#3,ZZ417,1%,WEEK,IFR,0/08:29:25,0/09:30:23,280,R,0000,EGXW,0/13:44:25,0/14:32:24,120,R,0000,EGXW,0/13:09:58,0/14:29:56,120,R,0000,EGXW,1/07:30:00,1/07:47:22,100,R,0000,EGYD,1/15:29:53,1/15:46:15,140,R,0000,EGXW,2/09:45:00,2/10:19:08,220,R,0000,EGVN,2/16:07:41,2/16:37:49,220,R,0000,EGXW,3/09:08:58,3/10:37:57,200,R,0000,EGSH

AC#4,ZZ418,1%,WEEK,IFR,0/07:59:53,0/08:28:43,220,R,0000,EGXW,5/08:59:39,5/12:46:32,350,R,0000,GCLP,5/12:58:22,5/18:43:16,350,R,0000,EGXW,6/07:28:15,6/08:21:09,180,R,0000,EGXW,6/10:13:08,6/10:32:49,180,R,0000,EGXW,6/12:13:43,6/12:38:19,280,R,0000,EGYM,6/14:58:36,6/15:23:34,280,R,0000,EGXW,2/13:58:29,2/15:11:56,350,R,0000,EGQS,2/07:59:11,2/09:22:38,350,R,0000,EGSH

AC#5,ZZ504,1%,WEEK,IFR,0/08:39:15,0/09:48:10,050,R,0000,EGXW,0/08:39:15,0/09:48:10,150,R,0000,EGXW,1/09:29:21,1/09:53:58,200,R,0000,EGXE,1/11:29:56,1/11:54:33,200,R,0000,EGXW,1/12:59:46,1/13:17:23,100,R,0000,EGXC,1/15:29:53,1/16:17:30,100,R,0000,EGXW,3/07:44:04,3/08:13:31,120,R,0000,EGSH,3/16:09:47,3/16:38:00,120,R,0000,EGXW,4/06:08:58,4/08:41:33,150,R,0000,EGXW

AC#6,ZZ419,1%,WEEK,IFR,0/09:17:29,0/09:34:09,200,R,0000,EGYD,0/14:28:43,0/14:45:23,200,R,0000,EGXW,1/09:28:08,1/11:56:07,350,R,0000,LIPA,2/11:28:43,2/13:56:42,350,R,0000,EGXW,3/13:29:18,3/13:44:04,180,R,0000,EGXW,4/15:29:53,4/15:44:39,180,R,0000,EGXW,4/17:28:00,4/18:06:00,280,R,0000,EGLF,5/08:29:04,5/09:07:26,280,R,0000,EGXW,5/15:04:53,5/15:22:15,200,R,0000,EGXC,6/08:28:43,6/08:46:23,200,R,0000,EGXW

PS: Sorry I didn't post the plans in a tx file or a zip file. I don't know how to post those here.

[Firebird]

A quick look shows that they validate w/o any errors.
The one thing I would say is that MIL aircraft and Airlines should always be F and a callsign number rather than R and 0000. The F will use the atc_airline parm from the fltsim entry whilst the R will use the atc_id parm which is the tail number.

One observation is that usually the last ICAO in each flightplan string is the home base. That is where the aircraft will take off from for its first trip. You have 2 a/c based at Norwich and 1 a/c at Farnorough. You could make the case for G-LBSB to be based at EGLF at the weekend but not really the others.

The only other point I would make is that if you are taking off and landing at the same airport unpredictable things can happen so you really should put in a TNG leg to somewhere.
For example if taking off from EGXW you should set a TNG leg at another base/waypoint before a second leg back to EGXW. If you want to simulate an aircraft doing TNGs at EGXW you should again have two legs. The first taking off from EGXW for TNGs at EGXW followed by a second leaving EGXW for EGXW for landing. The time difference between the arrival time at the TNG base and the departure back home should be between 0-5 mins or the aircraft either disappears or goes into an infinite loop. Our standard is to use 3 mins between the two times to be safe.

[Joseph29]

Thank you Steve. I changed the R's to F's. I have to go in about 20 minutes so I will make the adjustment of having the last ICAO airport in the plan as EGXW when I get back later tonight. I never knew about that being the home base airport.


Also is this a correct way of writing a TNG? EGXW,1/14:20:59,TNG1/14:25:30,100,F,0000,EGXW. I never wrote a TNG in a plan before. I got that one from a flightplan and just changed the time and airports to what I needed. I will have to look at some MAIW plans that have TNG's to see.

[Firebird]

That is the correct format. The 0000 you would change to whatever number you wanted as part of the callsign. If you are using AIFP to help you program then the thing about TNG legs is that you have to include enough time to transit from the departure point to wherever you are doing the approaches then add on the amount of time that you want to spend on approaches. Before you start the return leg.

One other thing don't program a TNG leg followed by another TNG leg as unpredictable things can happen, so don't plan a flight to go to , for example, 3 waypoints before returning home.
In most cases think of each flight having two legs. This also takes into something as an away night stop. The obvious difference is a tour where you never return to the point of origin except at the end of each week, and to be honest theses would be rare in military terms.

[Joseph29]

Ok here are the updated plans. How are the altitudes? Do they need to be adjusted/fixed? Also you said that I should change the 0000 to whatever number I want. Should that number be the same for the whole plan? For instance 1654 will be used for the whole G-LBSB plan?

AC#1,G-LBSB,1%,WEEK,IFR,0/10:23:51,TNG0/10:33:45,020,F,0000,EGXW,0/13:59:11,TNG0/14:09:57,020,F,0000,EGXW,1/09:19:31,1/10:03:39,300,F,0000,EGOV,2/14:10:47,2/15:31:55,300,F,0000,EGXW,3/09:11:26,3/10:06:34,350,F,0000,EGPK,3/15:26:47,3/16:21:18,350,F,0000,EGXW,4/09:00:00,TNG4/09:10:03,020,F,0000,EGXW,5/09:23:02,5/09:50:24,200,F,0000,EGUN,5/12:15:18,5/13:06:36,350,F,0000,EGNT,5/13:48:49,5/14:27:07,220,F,0000,EGXW,6/09:14:04,TNG6/09:24:58,020,F,0000,EGXW

AC#2,ZZ416,1%,WEEK,IFR,0/09:11:15,TNG0/09:15:11,020,F,0000,EGXW,0/12:56:26,TNG0/13:06:22,020,F,0000,EGXW,1/14:20:59,TNG1/14:30:30,020,F,0000,EGXW,2/09:19:10,2/10:04:38,350,F,0000,EGDY,2/12:24:58,2/13:09:24,350,F,0000,EGXC,2/15:44:18,2/16:02:00,200,F,0000,EGXW,3/09:32:21,TNG3/09:42:24,020,F,0000,EGXW,4/11:58:25,4/12:36:16,300,F,0000,EGLF,6/07:16:43,6/07:55:23,200,F,0000,EGXW

AC#3,ZZ417,1%,WEEK,IFR,0/08:29:25,TNG0/08:39:23,020,F,0000,EGXW,0/13:44:25,TNG0/13:55:24,020,F,0000,EGXW,0/13:09:58,TNG0/13:19:56,020,F,0000,EGXW,1/07:30:00,1/07:47:22,100,F,0000,EGYD,1/15:29:53,1/15:46:15,140,F,0000,EGXW,2/09:45:00,2/10:19:08,220,F,0000,EGVN,2/16:07:41,2/16:37:49,220,F,0000,EGXW,3/09:08:58,3/10:37:57,200,F,0000,EGSH,6/08:28:43,6/08:57:23,200,F,0000,EGXW

AC#4,ZZ418,1%,WEEK,IFR,0/07:59:53,TNG0/08:09:43,020,F,0000,EGXW,5/08:59:39,5/12:46:32,350,F,0000,GCLP,5/12:58:22,5/18:43:16,350,F,0000,EGXW,6/07:28:15,TNG6/07:38:09,020,F,0000,EGXW,6/10:13:08,TNG6/10:23:49,020,F,0000,EGXW,6/12:13:43,6/12:38:19,280,F,0000,EGYM,6/14:58:36,6/15:23:34,280,F,0000,EGXW,2/13:58:29,2/15:11:56,350,F,0000,EGQS,2/07:59:11,2/09:22:38,350,F,0000,EGSH,6/11:28:43,6/11:57:23,220,F,0000,EGXW

AC#5,ZZ504,1%,WEEK,IFR,0/08:39:15,TNG0/08:49:10,050,F,0000,EGXW,0/11:39:15,TNG0/11:49:10,020,F,0000,EGXW,1/09:29:21,1/09:53:58,200,F,0000,EGXE,1/11:29:56,1/11:54:33,200,F,0000,EGXW,1/12:59:46,1/13:17:23,100,F,0000,EGXC,1/15:29:53,1/16:17:30,100,F,0000,EGXW,3/07:44:04,3/08:13:31,120,F,0000,EGSH,3/16:09:47,3/16:38:00,120,F,0000,EGXW,4/09:08:58,TNG4/09:18:33,020,F,0000,EGXW

AC#6,ZZ419,1%,WEEK,IFR,0/09:17:29,0/09:34:09,200,F,0000,EGYD,0/14:28:43,0/14:45:23,200,F,0000,EGXW,1/09:28:08,1/11:56:07,350,F,0000,LIPA,2/11:28:43,2/13:56:42,350,F,0000,EGXW,3/13:29:18,TNG3/13:39:04,020,F,0000,EGXW,4/15:29:53,TNG4/15:39:39,020,F,0000,EGXW,4/17:28:00,4/18:06:00,280,F,0000,EGLF,5/08:29:04,5/09:07:26,280,F,0000,EGXW,5/15:04:53,5/15:22:15,200,F,0000,EGXC,6/08:28:43,6/08:46:23,200,F,0000,EGXW

[Greg]

Ok here are the updated plans. How are the altitudes? Do they need to be adjusted/fixed?

The general rule since the PAI days is to take the distance in NM and convert that to the nearest IFR flight level taking into account the semicircular rules and the service ceiling of the type. In real life there are many many factors to take into account so this general rule doesn't always make sense operationally, but it usually ensures that the AI engine can manage the climb and descent.

Also you said that I should change the 0000 to whatever number I want. Should that number be the same for the whole plan? For instance 1654 will be used for the whole G-LBSB plan?

Technically, it can be whatever you want and can be different for every leg. But a good flightplan requires some research.

Some quick googling revealed that the RAF Shadows usually take the first and last digit of their registration. If your fltsim entry mentions a tactical callsign, like "KNIGHT" for ZZ416, then you would write "0046" in the flightplan which then makes "KNIGHT FOUR SIX" in the sim. Tactical callsigns are usually only used within the country. When going abroad, an ICAO published callsign is normally used. In the case of the Shadows "ASCOT 74##" according to my source. If you give the fltsim entry the callsign "ASCOT" and you write "7446" in the flightplan, the callsign for that leg in the sim becomes "ASCOT SEVEN FOUR FOUR SIX"

G-LBSB seems to be an exception and uses its registration.

[Firebird]

On the height for the aircraft there are a couple of things to take into account. The height of the terrain you would be flying over, remember that VFR flights do not get adjusted for terrain. The second is the cruising height or the max height for that type. These can be typically found in things like wikipedia.
These set the min and max to be used but it makes a lot of sense to follow Gregs suggestion as long as the height falls in between the min and the max.

On the callsign front it depends on the aircraft. Some will have same callsign number for the entire day or week, but these generally fall into the category of transport or maritime aircraft. Most fast jets tend to change from sortie to sortie. To give you an example on my fast jet Squadrons, the sorties were planned and numbered from the bottom of the number range to the top. The aircraft were added to the sorties according to fit and availability. Changing the number meant that you couldn't easily track where each aircraft was.

[jimrodger]

Re. The ASCOT callsign...pretty sure that it was the sole reserve of what was historically 38Gp/Transport Command aircraft. eg VC10/C130 etc. It stood for "Air Support Command Operational Task".

The rest of us minions used RAFAIR (with a similar 4 digit number) when transitting abroad.

The callsigns allocated tended to be squadron assigned within their own country but after adoption of the NATO wide ATO (Air Tasking Order) tactical callsigns with a number eg SPIDER34 would be allocated to a force along with a block of numbers for relief aircraft etc. For example the Nimrod fleet during Afghan/Iraq would use SPIDER and be allocated a block 31-36, we would rotate through the allocation until all used up and start at the beginning again, or start with a new callsign.

Occasionally for special occasions we could decide on our own callsign, so Guernsey has been used for 201Sqn, Octopus for 206, Falcon for 120 as well as the well known Kipper callsign, but these tended to be for non-operational sorties.

Local area sorties eg Post major test-flights would use a Kin callsign and I'm pretty sure most bases would use the same convention.



HTH

Jim

[Joseph29]

I changed the F,0000 to R,0000 in the G-LBSB and added the flight numbers to the rest of the plans.

About the callsigns. I didn't know what the callsing was so I had AIRFOCRE, but changed them to KNIGHT since my plans have the planes mostly flying in the UK.

About the altitudes. I don't really know what you guys are talking about (when Greg said, take the distance in NM and convert that to the nearest IFR flight level) so I am going to leave the altitudes as they are.

[Greg]

About the altitudes. I don't really know what you guys are talking about (when Greg said, take the distance in NM and convert that to the nearest IFR flight level) so I am going to leave the altitudes as they are.

Calculate the distance between the two points. EGXW-EGPK for example is 200 nautical miles. Round that number to a valid flight level, in this case FL200. Apply the semi-circular rule (basically even levels for westbound traffic and odd levels for eastbound traffic). My final level is FL200.

Another example: EGNT-EGXW is 120NM. Round it off and you have FL120. However, the direction is eastbound so you need an odd flight level. I pick a level higher and my final level is FL130.

[Firebird]

The idea that Greg is trying to promote is that even if a plane can get to FL250 would it if the flight distance was 60nm?
No point in expending fuel to get up that high, and then start your descent before you make it to that altitude.

[Joseph29]

Thanks guys. I understand the Altitude thing now. I will adjust the altitudes now. If you guys think they are good enough I will send them to the MAIW download area so everyone can enjoy them.

[Joseph29]

What would the altitude be for a plane doing TNG's?

[Firebird]

It doesn't matter as the TNGs are a terminal thing and decided by the airfield the altitude in the flight plan is the transit altitude.

[Joseph29]

Here is my next plans. These are for VMM-363. There are paints and plans for these but the plans have them at Miramar. According to scramble.nl VMM-363 is now based at Kaneohe Bay. I took the MAIW P-3 Orion (the ones based at Kaneohe Bay) plans and adjusted the times and airports. I am not sure about the flight numbers so I left them as is. If anyone knows how VMM-363 do the flight numbers I will change them.


AC#1,168352,1%,WEEK,IFR,0/12:58:50,TNG0/15:00:17,010,F,0020,PHNG,1/07:20:31,1/08:15:34,160,F,0020,PHSF,1/16:58:50,1/17:53:17,160,F,0020,PHNG,2/09:11:31,TNG2/10:30:34,010,F,0020,PHNG,2/11:38:50,2/12:22:17,120,F,0020,PHBK,2/17:15:31,2/17:59:34,120,F,0020,PHNG,3/07:30:50,TNG3/10:40:17,010,F,0020,PHNG,3/19:00:31,TNG3/19:30:34,010,F,0020,PHNG,4/09:42:50,4/10:01:17,015,F,0020,PHHI,4/14:25:31,4/14:44:34,015,F,0020,PHNG

AC#2,166390,1%,WEEK,IFR,0/06:17:50,TNG0/06:42:17,010,F,0021,PHNG,0/09:20:31,0/10:04:34,115,F,0021,PHBK,0/14:24:50,0/15:08:17,115,F,0021,PHNG,1/11:10:31,TNG1/11:20:34,010,F,0021,PHNG,2/09:10:50,2/09:29:17,015,F,0021,PHHI,2/17:20:31,2/17:39:34,015,F,0021,PHNG,3/06:18:50,TNG3/06:28:17,010,F,0021,PHNG,3/15:20:31,TNG3/15:30:34,010,F,0021,PHNG,4/11:27:50,4/11:48:17,025,F,0021,PHDH,5/19:40:31,5/20:01:34,025,F,0021,PHNG

AC#3,168642,1%,WEEK,IFR,0/10:12:50,TNG0/11:52:17,010,F,0022,PHNG,1/10:22:31,1/10:41:34,015,F,0022,PHHI,1/16:05:50,1/16:24:17,015,F,0022,PHNG,1/18:10:31,TNG1/18:20:34,010,F,0022,PHNG,2/11:24:50,2/11:45:17,025,F,0022,PHDH,2/15:20:31,2/15:41:34,025,F,0022,PHNG,3/09:22:50,TNG3/09:32:17,010,F,0022,PHNG,3/14:00:31,TNG3/14:10:34,010,F,0022,PHNG,4/06:22:50,4/06:41:17,015,F,0022,PHHI,6/17:54:31,6/18:13:34,015,F,0022,PHNG

AC#4,168604,1%,WEEK,IFR,1/18:00:00,TNG1/18:20:55,010,F,0030,PHNG,2/10:03:48,TNG2/10:13:31,010,F,0030,PHNG,3/08:00:00,3/08:55:55,160,F,0030,PHSF,3/16:23:48,3/17:18:31,160,F,0030,PHNG,4/18:00:00,TNG4/18:10:55,010,F,0030,PHNG,5/11:33:48,TNG5/11:44:31,010,F,0030,PHNG,6/10:00:00,6/10:44:55,120,F,0030,PHBK,6/16:57:48,6/17:41:31,120,F,0030,PHNG,0/11:24:00,TNG0/11:34:55,010,F,0030,PHNG,0/14:23:48,TNG0/14:33:31,010,F,0030,PHNG

AC#5,168322,1%,WEEK,IFR,1/18:00:00,TNG1/18:20:55,010,F,0031,PHNG,2/10:15:27,2/10:36:10,025,F,0031,PHDH,2/20:20:00,2/20:41:55,025,F,0031,PHNG,3/08:09:27,TNG3/10:00:10,010,F,0031,PHNG,3/13:00:00,TNG3/13:27:55,010,F,0031,PHNG,3/18:23:27,3/18:42:10,015,F,0031,PHHI,4/08:10:00,4/08:19:55,015,F,0031,PHNG,5/07:43:27,TNG5/08:33:10,010,F,0031,PHNG,5/09:18:00,5/10:02:55,120,F,0031,PHBK,5/16:15:27,5/16:59:10,120,F,0031,PHNG

AC#6,168022,1%,WEEK,IFR,1/18:59:04,TNG1/19:17:31,055,F,0040,PHNG,2/09:21:45,2/09:42:48,025,F,0040,PHDH,2/18:22:04,2/18:43:31,025,F,0040,PHNG,2/19:21:45,TNG2/19:39:48,055,F,0040,PHNG,3/07:20:04,3/08:15:31,160,F,0040,PHSF,3/16:11:45,3/17:06:48,160,F,0040,PHNG,4/08:19:04,TNG4/08:29:31,010,F,0040,PHNG,4/19:21:45,TNG4/19:31:48,010,F,0040,PHNG,5/11:49:04,TNG5/11:59:31,010,F,0040,PHNG,5/19:21:45,TNG5/19:31:48,010,F,0040,PHNG

AC#7,168286,1%,WEEK,IFR,1/11:09:04,TNG1/11:19:31,010,F,0041,PHNG,1/19:21:45,1/19:40:48,015,F,0041,PHHI,2/06:59:04,2/07:18:31,015,F,0041,PHNG,2/12:11:45,2/12:55:48,120,F,0041,PHBK,3/18:59:04,TNG3/19:09:31,010,F,0041,PHBK,3/09:21:45,3/10:05:48,120,F,0041,PHNG,4/11:24:04,TNG4/13:42:31,010,F,0041,PHNG,4/19:11:45,4/20:06:48,160,F,0041,PHSF,5/08:16:04,5/09:11:31,160,F,0041,PHNG,5/19:30:45,TNG5/19:40:48,010,F,0041,PHNG

AC#8,167917,1%,WEEK,IFR,1/11:59:04,TNG1/13:19:31,010,F,0042,PHNG,1/19:34:45,1/19:55:48,025,F,0042,PHDH,2/06:27:04,2/06:48:31,025,F,0042,PHNG,2/16:00:45,2/16:19:48,015,F,0042,PHHI,3/11:22:04,3/11:43:31,015,F,0042,PHNG,3/19:11:45,TNG3/19:22:48,010,F,0042,PHNG,4/15:11:04,4/15:34:31,025,F,0042,PHDH,4/17:01:45,4/17:22:48,025,F,0042,PHNG,5/08:16:04,5/09:00:31,120,F,0042,PHBK,5/16:44:45,5/17:28:48,120,F,0042,PHNG

[Joseph29]

I want to make new plans for the USAF CV-22B based at Mildenhall next. I know these were done, but they are 24HR plans and only do TNG's at Mildenhall. I want to make WEEK plans and send them to a few other airports (if they do fly to other airports). What other airports could I send them to that would be realistic?

[Victory103]

On the other thread I did make a few basic plans for Kbay based -363. Use the normal numbers for callsigns like lead is 11, wing 12. Real world the V22s don’t fly that high due to O2 requirements. Google the EGUN Ospreys and one was broke down at an old RAF base they use for training. Ideally though they are high demand assets and deploy quite a bit. In the photo thread you’ll see one visited RIAT this year. In some of the packages, the FPs are made with the quick generated spreadsheet to get the models flying in sim. I go back in and adjust them when I have time. Not up on UK flights, but US stuff is easy to determine. Also for callsigns, if I can’t find one I just use the unit mascot.

[swp53]

Re:
"I want to make new plans for the USAF CV-22B based at Mildenhall next. I know these were done, but they are 24HR plans and only do TNG's at Mildenhall. I want to make WEEK plans and send them to a few other airports (if they do fly to other airports). What other airports could I send them to that would be realistic?"

Look up the transponder code for each aircraft at site like http://www.airport-data.com/.
Example CV-22B 11-0057 of 7th SOS Mildenhall shows Mode S (ICAO24) Code: AE5409
Go to https://flight-data.adsbexchange.com/ and enter AE5409 in the Enter Icao box and press submit. You will then get a list of flights by date with the most recent at the top. Click on the date and you will get a track of when it was picked up on SSR radar and when it was lost from radar this will be due to the height it was flying at. Try a few dates and pick some routes from that. Looking at 28th August for this aircraft it was picked up South of Mildenhall and lost to the East which looks like it was flying a simple circuit. But 10th July is a much more complex flight.
You can zoom in on the map to get an idea of take off and landing locations.
You may want to make a few waypoints for flights that take off and land at the same location but are not circuits.
Hope this helps.
Steve

You could do the same with your previous SHADOW R1 flight plans.
Also some other callsigns for the Shadow's are: MADUSA, SCARAB, SERPENT, SNAKE, SNOOPER, VULCAN, WAD, WIDGIT.
Vulcan and Wad are followed by 01, 02 erc rather than the first and last number of the tail code.
Shadow R1
G-LBSB Mode S transponder: 4069D9
ZZ416 Mode S transponder: 43C2B2
ZZ417 Mode S transponder: 43C2B3
ZZ418 Mode S transponder: 43C2B4
ZZ419 Mode S transponder: 43C2B5
ZZ504 Mode S transponder: 43C61D

[Joseph29]

Thanks for the tip swp53.

And just so everyone knows the registrations I used for the VMM-363 plans are not current. The registrations used are the ones that were painted on the JYAI model.

[Victory103]

I was using ads-b exchange real world to track my unit's flights, another great resource for mil flights.

@Joseph29, like many of the packages you have to do the "snapshot" as airframes are moved around alot real world, especially I have found with the USN F-18s. I looking to populate a few more Super Bug squadrons as the legacy Hornet is becoming no more in fleet service and find the serial numbers (Bunos) are hard to read anyway in the paints. In the case of the V-22s, as long as you have the CO/CAG color bird and the rest low vis line aircraft, it works.