AEFAF3 08-3178 C-130J

[Snoop56]

Flew for second time yesterday

AEFAF3 08-3178 C-130J 317thAW Dyess

Jason....................

[Albert]

Flew for second time yesterday

AEFAF3 08-3178 C-130J 317thAW Dyess

Jason....................

Jason, Thanks! Strange code!

Albert

[Trubb]

Hi Albert/Jason

I presume this is a miscode (or a typo) given that AE4AF3 was reported in the Atlanta area yesterday with Mode S flight ID "LAC5673" which is the construction number/msn of 08-3178.

Best wishes

Trubb

[Snoop56]

Hi Thubb

This was what he was showing on his transponder when my mate who lives at Dobbins shot it yesterday, im not to up on hexcodes why wud this be a miscode?

Regards

Jason..................

Hi Albert/Jason

I presume this is a miscode (or a typo) given that AE4AF3 was reported in the Atlanta area yesterday with Mode S flight ID "LAC5673" which is the construction number/msn of 08-3178.

Best wishes

Trubb

[Trubb]

Hi Jason

If the transponder was emitting AEFAF3 it would be a miscode given that (as I mentioned in my previous posting) that similar hex code AE4AF3 was also reported in the Atlanta area on Thursday, using Mode S Flight ID (or callsign if you prefer) of "LAC5673" and this indicates that it (AE4AF3) was being used by the C-130 with constructors number/msn "5673", which happens to be C-130J 08-3178.

It's also worth noting that hex codes AE4AF0 through to AE4AF2 are assigned to C-130Js 08-3175 to 08-3177 so the next in sequence would be AE4AF3 = 08-3178 and that is supported by what I have said above.

Lastly, as Albert has alluded to, AEF*** is a strange hex code, given that all new US military aircraft are being assigned hex codes in the AE4*** block, so anything higher than that must be a miscode.

All things considered it looks to me that...
AE4AF3 = 08-3178; and
AEFAF3 = 08-3178 (miscoded)

Best wishes

Trubb

[Snoop56]

Thankyou Thubb it makes more sense to me now so i understand what you mean now, As i said before Hexcodes are not my strong point but maybe Albert can change this one and enter the others your said in due course?.

Regards

Jason.......................

Hi Jason

If the transponder was emitting AEFAF3 it would be a miscode given that (as I mentioned in my previous posting) that similar hex code AE4AF3 was also reported in the Atlanta area on Thursday, using Mode S Flight ID (or callsign if you prefer) of "LAC5673" and this indicates that it (AE4AF3) was being used by the C-130 with constructors number/msn "5673", which happens to be C-130J 08-3178.

It's also worth noting that hex codes AE4AF0 through to AE4AF3 are assigned to C-130Js 08-3175 to 08-3177 so the next in sequence would be AE4AF3 = 08-3178 and that is supported by what I have said above.

Lastly, as Albert has alluded to, AEF*** is a strange hex code, given that all new US military aircraft are being assigned hex codes in the AE4*** block, so anything higher than that must be a miscode.

All things considered it looks to me that...
AE4AF3 = 08-3178; and
AEFAF3 = 08-3178 (miscoded)

Best wishes

Trubb

[Navairboss]

Morning aLL,

I saw this one fly on 9/8/2011 with the proper code of AE4AF3 and a Mode-S call of LAC 5673. I did not see the 9/9/ second flight up here north of Atlanta so I cannot confirm the miscode of AEFAF3.

So Albert for the db, they didn't conduct that second flight up here, but they did have the proper code on the first flight of AE4AF3 on 9/8 and that is in the database in my location and also seen on the ATL box.

73 de Larry
Brasstown NC

[Snoop56]

Albert

Just to add as i see you ahve updated this batch that they are all heading for Dyess AFB as the unit.

Regards

Jason...................

[Albert]

Albert

Just to add as i see you ahve updated this batch that they are all heading for Dyess AFB as the unit.

Regards

Jason...................

Jason,

Units will be updated in 1 minute.

Albert