Navy Inventory Records: Difference between revisions

From Invader Historical Foundation
Jump to navigation Jump to search
 
(21 intermediate revisions by the same user not shown)
Line 213: Line 213:
==VU-4==
==VU-4==


VU-4 was Utility Squadron 4. They were based out of Chincoteague.  
VU-4 was Utility Squadron 4. They were based out of Chincoteague. <br/>
The 2nd JD-1D that shows up to the squadron in Oct 1956 is the former XJD-1 Prototype, [[57990]].  


{| class="wikitable sortable"
{| class="wikitable sortable"
Line 322: Line 323:
<P>
<P>
<P>
<P>


==VU-10==
==VU-10==
Line 496: Line 495:
|-
|-
|}
|}




Line 546: Line 546:
<P>
<P>
<P>
<P>


==Atlantic Command Summary==
==Atlantic Command Summary==
Line 1,035: Line 1,033:
|-
|-
|Nov 1956
|Nov 1956
|JD-1
|D1 (In Overhaul)
|3
|-
|Dec 1956
|JD-1
|JD-1
|D1 (In Overhaul)
|D1 (In Overhaul)
Line 1,042: Line 1,045:




Squadron Count - This table summarizes the total count of the squadron's Invaders each month, regardless of status.  
===Oppama Squadron Count===
This table summarizes the total count of the squadron's Invaders each month, regardless of status.  
 
{| class="wikitable sortable"
{| class="wikitable sortable"
! Period
! Period
Line 1,059: Line 1,064:
|-
|-
|Nov 1956
|Nov 1956
|3
|0
|0
|0
|3
|-
|Dec 1956
|3
|3
|0
|0
Line 1,074: Line 1,086:
<P>
<P>
<P>
<P>


==Pacific Command Summary==
==Pacific Command Summary==
Line 1,112: Line 1,122:
|34
|34
|-
|-
|}
|Dec 1956
 
|6
 
|1
|11
|13
|3
|34
|-
|}
 
 
<P>
<P>
<P>
<P>
Line 1,121: Line 1,139:
<P>
<P>
<P>
<P>


=Research & Development, BAUER (R&D)=
=Research & Development, BAUER (R&D)=
Line 1,170: Line 1,186:
|A9 (R&D, Aging)
|A9 (R&D, Aging)
|2
|2
|-
|Dec 1956
|JD-1
|A9 (R&D, Aging)
|1
|-
|Dec 1956
|JD-1D
|A9 (R&D, Aging)
|4
|-
|-
|}
|}




Squadron Count - This table summarizes the total count of the squadron's Invaders each month, regardless of status.  
===R&D Squadron Count===
This table summarizes the total count of the squadron's Invaders each month, regardless of status.  
 
{| class="wikitable sortable"
{| class="wikitable sortable"
! Period
! Period
Line 1,203: Line 1,231:
|0
|0
|3
|3
|-
|Dec 1956
|1
|4
|0
|0
|5
|-
|-
|}
|}
Line 1,213: Line 1,248:
<P>
<P>
<P>
<P>


==NATC Patuxent River==
==NATC Patuxent River==
Line 1,237: Line 1,270:
|-
|-
|Nov 1956
|Nov 1956
|JD-1
|A9 (R&D, Aging)
|1
|-
|Dec 1956
|JD-1
|JD-1
|A9 (R&D, Aging)
|A9 (R&D, Aging)
Line 1,244: Line 1,282:




Squadron Count - This table summarizes the total count of the squadron's Invaders each month, regardless of status.  
===Pax River Squadron Count===
This table summarizes the total count of the squadron's Invaders each month, regardless of status.  
 
{| class="wikitable sortable"
{| class="wikitable sortable"
! Period
! Period
Line 1,268: Line 1,308:
|-
|-
|Nov 1956
|Nov 1956
|1
|0
|0
|0
|1
|-
|Dec 1956
|1
|1
|0
|0
Line 1,283: Line 1,330:
<P>
<P>
<P>
<P>


==NAMTC Point Mugu==
==NAMTC Point Mugu==
Line 1,307: Line 1,352:
|-
|-
|Nov 1956
|Nov 1956
|JD-1D
|AR (R&D, Not-Aging)
|2
|-
|Dec 1956
|JD-1D
|JD-1D
|AR (R&D, Not-Aging)
|AR (R&D, Not-Aging)
Line 1,314: Line 1,364:




Squadron Count - This table summarizes the total count of the squadron's Invaders each month, regardless of status.  
===Point Mugu Squadron Count===
This table summarizes the total count of the squadron's Invaders each month, regardless of status.  
 
{| class="wikitable sortable"
{| class="wikitable sortable"
! Period
! Period
Line 1,344: Line 1,396:
|2
|2
|-
|-
|}
|Dec 1956
|0
|2
|0
|0
|2
|-
|}




Line 1,353: Line 1,412:
<P>
<P>
<P>
<P>


==Research & Development Command Summary==
==Research & Development Command Summary==
Line 1,382: Line 1,439:
|2
|2
|6
|6
|-
|Dec 1956
|5
|1
|2
|8
|-
|-
|}
|}
Line 1,392: Line 1,455:
<P>
<P>
<P>
<P>


=Field Activities, Bureau of Aeronautics (BAUER)=
=Field Activities, Bureau of Aeronautics (BAUER)=
Line 1,404: Line 1,465:
==O&R Norfolk==
==O&R Norfolk==


Overhaul & Repair Center Norfolk was a major repair and conversion depot servicing the East Coast.  
Overhaul & Repair Center Norfolk was a major repair and conversion depot servicing the East Coast. <br/>
One of the 4 JD-1Ds with status code B in Sept 1956 is the original XJD-1 Prototype, [[57990]].  


{| class="wikitable sortable"
{| class="wikitable sortable"
Line 1,531: Line 1,593:
|D4 (Conversion)
|D4 (Conversion)
|3
|3
|}
Squadron Count - This table summarizes the total count of the squadron's Invaders each month, regardless of status.
{| class="wikitable sortable"
! Period
! JD-1
! JD-1D
! JD-1X
! JD-1DX
! Total
|-
|-
|Sep 1956
|Dec 1956
|8
|JD-1
|4
|B (Awaiting Assignment)
|13
|2
|4
|-
|29
|Dec 1956
|JD-1
|DA (Overhaul Complete, Pending flight check)
|2
|-
|-
|Oct 1956
|Dec 1956
|12
|JD-1
|0
|D1 (Overhaul Complete)
|13
|5
|5
|30
|-
|-
|Nov 1956
|Dec 1956
|12
|JD-1
|4
|E1 (Overhaul onsite, flyable)
|10
|3
|4
|-
|30
|Dec 1956
|JD-1
|G5 (Modification)
|1
|-
|Dec 1956
|JD-1X
|E4 (Overhaul Conversion in place, Flyable)
|10
|-
|Dec 1956
|JD-1D
|C (En route to base, flying)
|1
|-
|Dec 1956
|JD-1DX
|D4 (Conversion)
|3
|-
|-
|}
|}




<P>
===Norfolk Squadron Count===
<P>
This table summarizes the total count of the squadron's Invaders each month, regardless of status.
<P>
<P>
<P>
<P>


 
{| class="wikitable sortable"
 
==O&R Quonset Pt==
 
Overhaul & Repair Center Quonset Point was a major repair and conversion depot servicing the northeast.
 
{| class="wikitable sortable"
! Period
! Type
! Status
! Number
|-
|Sep 1956
|JD-1
|EN (Transfer for Rework, Non-flyable)
|1
|-
|}
 
 
Squadron Count - This table summarizes the total count of the squadron's Invaders each month, regardless of status.
{| class="wikitable sortable"
! Period
! Period
! JD-1
! JD-1
Line 1,604: Line 1,649:
|-
|-
|Sep 1956
|Sep 1956
|1
|8
|0
|4
|0
|13
|0
|4
|1
|29
|-
|-
|Oct 1956
|Oct 1956
|12
|0
|0
|0
|13
|0
|5
|0
|30
|0
|-
|-
|Nov 1956
|Nov 1956
|0
|12
|0
|4
|0
|10
|0
|4
|0
|30
|-
|Dec 1956
|13
|1
|10
|3
|27
|-
|-
|}
|}
Line 1,634: Line 1,686:
<P>
<P>


==O&R Quonset Pt==


 
Overhaul & Repair Center Quonset Point was a major repair and conversion depot servicing the northeast.  
==Litchfield Park==
 
Litchfield Park is a US Navy Storage Facility (aka:Boneyard).  


{| class="wikitable sortable"
{| class="wikitable sortable"
Line 1,648: Line 1,698:
|Sep 1956
|Sep 1956
|JD-1
|JD-1
|MX (Storage, Rework Req. Not in CANS)
|EN (Transfer for Rework, Non-flyable)
|3
|1
|-
|}
 
 
===Quonset Point Squadron Count===
This table summarizes the total count of the squadron's Invaders each month, regardless of status.  
 
{| class="wikitable sortable"
! Period
! JD-1
! JD-1D
! JD-1X
! JD-1DX
! Total
|-
|-
|Sep 1956
|Sep 1956
|JD-1X
|1
|M4 (Storage, Conversion Rework Required)
|0
|11
|0
|-
|0
|Oct 1956
|1
|JD-1
|MX (Storage, Rework Req. Not in CANS)
|2
|-
|-
|Oct 1956
|Oct 1956
|JD-1X
|0
|M4 (Storage, Conversion Rework Required)
|0
|11
|0
|0
|0
|-
|-
|Nov 1956
|Nov 1956
|JD-1
|0
|MX (Storage, Rework Req. Not in CANS)
|0
|2
|0
|0
|0
|-
|-
|Nov 1956
|Dec 1956
|JD-1X
|0
|M4 (Storage, Conversion Rework Required)
|0
|11
|0
|0
|0
|-
|-
|}
|}




Squadron Count - This table summarizes the total count of the squadron's Invaders each month, regardless of status.  
<P>
<P>
<P>
<P>
<P>
<P>
 
==Litchfield Park==
 
Litchfield Park is a US Navy Storage Facility (aka:Boneyard).  
 
{| class="wikitable sortable"
{| class="wikitable sortable"
! Period
! Period
! JD-1
! Type
! JD-1D
! Status
! JD-1X
! Number
! JD-1DX
! Total
|-
|-
|Sep 1956
|Sep 1956
|3
|JD-1
|0
|MX (Storage, Rework Req. Not in CANS)
|3  
|-
|Sep 1956
|JD-1X
|M4 (Storage, Conversion Rework Required)
|11
|11
|0
|14
|-
|-
|Oct 1956
|Oct 1956
|2
|JD-1
|0
|MX (Storage, Rework Req. Not in CANS)
|2  
|-
|Oct 1956
|JD-1X
|M4 (Storage, Conversion Rework Required)
|11
|11
|0
|13
|-
|-
|Nov 1956
|Nov 1956
|2
|JD-1
|0
|MX (Storage, Rework Req. Not in CANS)
|2  
|-
|Nov 1956
|JD-1X
|M4 (Storage, Conversion Rework Required)
|11
|-
|Dec 1956
|JD-1
|MX (Storage, Rework Req. Not in CANS)
|1
|-
|Dec 1956
|JD-1X
|M4 (Storage, Conversion Rework Required)
|11
|11
|0
|13
|-
|-
|}
|}




<P>
===Litchfield Park Squadron Count===  
<P>
This table summarizes the total count of the squadron's Invaders each month, regardless of status.
<P>
<P>
<P>
<P>
 
 
 
==Bureau of Aeronautics Command Summary==


{| class="wikitable sortable"
{| class="wikitable sortable"
!Date
! Period
! Norfolk
! JD-1
! Quonset
! JD-1D
! Litchfield
! JD-1X
! JD-1DX
! Total
! Total
|-
|-
|Sep 1956
|Sep 1956
|29
|3
|1
|0
|11
|0
|14
|14
|44
|-
|-
|Oct 1956
|Oct 1956
|30
|2
|0
|11
|0
|0
|13
|13
|43
|-
|-
|Nov 1956
|Nov 1956
|30
|2
|0
|11
|0
|0
|13
|13
|43
|-
|Dec 1956
|1
|0
|11
|0
|12
|-
|-
|}
|}
Line 1,758: Line 1,855:
<P>
<P>


==Bureau of Aeronautics Command Summary==


 
{| class="wikitable sortable"
=US Navy Total Summary=
Preliminary thoughts regarding the table below. We know from the Bureau Number list that the US Navy had 150 JD-1s and 2 XJD-1s in total. The XJD-1s began service life with the Navy in March 1946. By the time time this report was started in Sep 1956 a decade has already passed. In that period 20 JD-1s are unaccounted for. At this time I do not know if they were destroyed in an accident or simply scrapped. As I get the individual aircraft records this will become clear. What is clear is that since none of the JD-1s were used in combat, none of the JD-1s were lost due to enemy action.
 
{| class="wikitable sortable"
!Date
!Date
! Atlantic
! Norfolk
! Pacific
! Quonset
! R&D
! Litchfield
! BAUER
! Total
! Total
|-
|-
|Sep 1956
|Sep 1956
|45
|29
|35
|1
|6
|14
|44
|44
|130
|-
|-
|Oct 1956
|Oct 1956
|46
|30
|33
|0
|6
|13
|43
|43
|128
|-
|-
|Nov 1956
|Nov 1956
|45
|30
|34
|0
|6
|13
|43
|43
|128
|-
|Dec 1956
|27
|0
|12
|39
|-
|-
|}
|}
<P>
<P>
<P>
<P>
<P>
<P>
=US Navy Total Summary=
Preliminary thoughts regarding the table below. We know from the Bureau Number list that the US Navy had 150 JD-1s and 2 XJD-1s in total. The XJD-1s began service life with the Navy in March 1946. By the time time this report was started in Sep 1956 a decade has already passed. In that period 20 JD-1s are unaccounted for. At this time I do not know if they were destroyed in an accident or simply scrapped. As I get the individual aircraft records this will become clear. What is clear is that since none of the JD-1s were used in combat, none of the JD-1s were lost due to enemy action.
{| class="wikitable sortable"
!Date
! Atlantic
! Pacific
! R&D
! BAUER
! Total
|-
|Sep 1956
|45
|35
|6
|44
|130
|-
|Oct 1956
|46
|33
|6
|43
|128
|-
|Nov 1956
|45
|34
|6
|43
|128
|-
|Dec 1956
|50
|34
|8
|39
|131
|-
|}
=Understanding the Inventory Codes=
All of the Allowances Reports use an alphanumeric code system to distinguish the status of the aircraft. I have abbreviated the codes in the tables above, but here I will provide additional explanations.
{| class="wikitable sortable"
!Status Code
!Definition
!Comments
|-
|A2
|Combat Services
|According to what I've been able to find, the Combat Services role deals primarily with transporting of goods or equipment into combat zones to support the combat personnel embroiled in the fight. I do know that several Invaders were modified in Africa to carry cargo pallets or fitted with seat pallets to serve as emergency transports, so its possible the JD-1s in this role could have been put to use along the same lines. I'll keep digging into this.
|-
|A8
|Utility, Aging
|Planes in the utility role were assigned to be target tugs or to act as air targets to be intercepted.
|-
|A9
|Research & Development
|
|-
|AK
|Combat Services, Not Aging
|
|-
|AQ
|Utility, Not Aging
|
|-
|AR
|R&D, Not-Aging.
|
|-
|B
|Awaiting Assignment
|This unit is usually Fully Mission Capable (FMC), but not assigned to a unit.
|-
|C
|en route, flying
|The plane is being moved by air to another location, usually an overhaul & repair depot.
|-
|C9
|en route, surface
|The plane has been loaded on a carrier and is being transported via sea to another location.
|-
|D1
|In Overhaul
|Usually engine changes and maintenance of that sort.
|-
|D2
|Progressive Maintenance, Conversion
|Combines Progressive maintenance with conversion to a different type, such as a JD-1 to a JD-1D, for example.
|-
|D3
|Progressive Maintenance
|
|-
|D4
|Overhaul Conversion
|Combines overhaul with conversion to a different type, such as JD-1 to JD-1D, for example.
|-
|DA
|Overhaul Complete except for flight check.
|
|-
|DB
|Progressive Maintenance conversion complete except for flight check
|
|-
|DC
|Progressive Maintenance Complete except for flight check
|
|-
|DD
|Overhaul conversion complete except for flight check
|
|-
|E1
|To be overhauled where located, flyable
|
|-
|E2
|To have progressive maintenance conversion where located, flyable
|
|-
|E3
|To have progressive maintenance where located, flyable.
|
|-
|E4
|To have overhaul conversion where located, flyable.
|
|-
|E6
|To be overhauled where located, not flyable
|
|-
|E7
|To have progressive maintenance conversion where located, not flyable
|
|-
|E8
|To have overhaul conversion where located, not flyable.
|
|-
|E9
|To have overhaul conversion where located, not flyable.
|
|-
|EJ
|To be overhauled elsewhere, flyable
|
|-
|EK
|To have progressive maintenance conversion elsewhere, flyable
|
|-
|EL
|To have progressive maintenance elsewhere, flyable.
|
|-
|EM
|To have overhaul conversion elsewhere, flyable.
|
|-
|EN
|To be overhauled elsewhere, not flyable
|
|-
|EP
|To have progressive maintenance conversion where located, not flyable
|
|-
|EQ
|To have overhaul conversion elsewhere, not flyable.
|
|-
|ER
|To have overhaul conversion elsewhere, not flyable.
|
|-
|F
|En route to rework
|This code is incomplete, but sometimes used. It should be followed with a number
|-
|F1
|En route for overhaul, flying
|
|-
|F2
|en route to progressive maintenance conversion, flying
|
|-
|F3
|en route to progressive maintenance, flying.
|
|-
|F4
|en route to overhaul conversion, flying.
|
|-
|F6
|en route tp overhaul, surface (Sea) transport
|
|-
|F7
|en route to progressive maintenance conversion, surface (Sea) transport
|
|-
|F8
|en route to overhaul conversion, surface (Sea) transport
|
|-
|F9
|en route to overhaul conversion, surface (Sea) transport
|-
|G4
|Conversion
|Conversion to a different type of plane.
|-
|G5
|Modification
|
|-
|G6
|Repair
|As the result from an accident.
|-
|G7
|Modernization
|
|-
|G8
|Modernization conversion
|
|-
|MX
|In storage-standard rework required, not in containers
|The aircraft is parked in one piece.
|-
|MY
|In storage-standard rework not required, not in containers
|the aircraft is parked in one piece.
|-
|Q1
|Awaiting strike decision, damage
|
|-
|P2
|Awaiting strike decision, depreciation, flyable
|
|-
|P3
|awaiting strike decision, administrative, flyable.
|
|-
|P4
|awaiting strike decision, Service life ended, flyable
|
|-
|RD
|struck while in process of standard rework.
|
|-
|}
==Aging vs Non-Aging==
Aircraft Non-Aging Record (OPNAV 4790/18)
The Aircraft Non-Aging Record is maintained as a part of the aircraft logbook to provide a permanent record of time accumulated in nonaging situations. To understand the purpose and use of this record, you must understand what is meant by aircraft aging and nonaging.
When an aircraft is purchased by the Navy, the Navy plans to operate the aircraft for a specified number of months, called operational service months (OPSERMOS). The total number of OPSERMOS expected before the aircraft is retired is the operational service life or planned service life of the aircraft. For example, an aircraft is purchased by the Navy with a planned service life of 60 OPSERMOS. This means 60 months of actual operational use. The days during which this aircraft is in storage, undergoing special rework at the depot facility, etc., do not count toward the planned service life of the aircraft; they are nonaging days. A properly maintained nonaging record in the logbook provides a record of all time periods that the aircraft was not aging, and will ultimately aid in the aircraft receiving its full operational service life.
The dates entered in block 6 of the nonaging record reflect the entire period the aircraft is out of service, including all transit, awaiting, and in-process time (pipeline).
The accumulative nonaging days are recorded in block 8. If an entry exceeds 30, or a multiple thereof, record 30, 60, 90, etc., in block 8 and the excess in block 9. Whenever 30, 60, 90, etc., is entered in block 8, an OPNAV XRAY is forwarded to modify the period end date 1 month for each 30-day increment. After the OPNAV XRAY report, the accumulated days in block 8 are reduced to zero. The next entry in block 8 will include the total in block 9 from prior incidents.
NOTE: Not mission capable (NMC) or partial mission capable (PMC) time is NOT recorded on the nonaging record.

Latest revision as of 19:44, 18 July 2022

The Navy Inventory Records are divided into two types of records. The first type is the Aircraft History Card. This is the Navy's equivalent of the USAF's Individual Aircraft Record Card. The AHC contains specific information about the status and movement of the plane. As I get these records, they will be transcribed individually on the plane's specific page. (So the AHC for BuNo 57990 will be transcribed on the page for that plane, etc).

The second type of inventory record is the "Allowances and Locations of Naval Aircraft" reports. These reports are compiled monthly and provide a high-level overview of every naval aviation unit, which types planes the unit is assigned, the number of planes assigned, and the status of those planes. Each of these reports is about 75 pages and has to be read through manually, so it takes some time. These reports are summarized below. They will also be repeated on the unit's specific page, once the overall transcription process is complete. Unfortunately, these reports did not begin until Sep 1956, so everything from March 1945 until Sep 1956 has no corresponding report. The unit strength for this period will have to be populated manually from the AHCs as they are transcribed.

For ease of transcribing the records I have listed them here by reporting group, which is how they appear on the report. That's the reason for the units being listed out of order in this fashion.

A NOTE: If you are comparing my Summary Totals below to the summary counts listed in the reports you may notice what appears to be a discrepancy. The data is accurate, however. In the US Navy Reports the summary totals only show Active, flyable aircraft and excludes any aircraft in overhaul or conversion. My summary totals below show all aircraft, regardless of status.

Atlantic Command (LANT)

VX-2

VX-2 was Operational Development Squadron 2. They were based out of Chincoteague.

Period Type Status Number
Sep 1956 JD-1 A9 (R&D, Aging) 1
Sep 1956 JD-1D A9 (R&D, Aging) 1
Oct 1956 JD-1 A9 (R&D, Aging) 1
Oct 1956 JD-1D A9 (R&D, Aging) 1
Nov 1956 JD-1 A9 (R&D, Aging) 1
Nov 1956 JD-1D A9 (R&D, Aging) 1
Dec 1956 JD-1 A9 (R&D, Aging) 1
Dec 1956 JD-1D A9 (R&D, Aging) 1


VX-2 Squadron Count

This table summarizes the total count of the squadron's Invaders each month, regardless of status.

Period JD-1 JD-1D JD-1X JD-1DX Total
Sep 1956 1 1 0 0 2
Oct 1956 1 1 0 0 2
Dec 1956 1 1 0 0 2
Dec 1956 1 1 0 0 2

VU-2

VU-2 was Utility Squadron 2. They were based out of Quonset Point.

Period Type Status Number
Sep 1956 JD-1 AQ (Utility, not Aging) 2
Sep 1956 JD-1 A8 (Utility, Aging) 10
Oct 1956 JD-1 AQ (Utility, not Aging) 2
Oct 1956 JD-1 A8 (utility, Aging) 10
Nov 1956 JD-1 AQ (Utility, not Aging) 2
Nov 1956 JD-1 A8 (utility, Aging) 9
Dec 1956 JD-1 AQ (Utility, not Aging) 3
Dec 1956 JD-1 A8 (utility, Aging) 8


VU-2 Squadron Count

This table summarizes the total count of the squadron's Invaders each month, regardless of status.

Period JD-1 JD-1D JD-1X JD-1DX Total
Sep 1956 12 0 0 0 12
Oct 1956 12 0 0 0 12
Nov 1956 11 0 0 0 11
Dec 1956 11 0 0 0 11

VU-4

VU-4 was Utility Squadron 4. They were based out of Chincoteague.
The 2nd JD-1D that shows up to the squadron in Oct 1956 is the former XJD-1 Prototype, 57990.

Period Type Status Number
Sep 1956 JD-1 A8 (Utility, Aging) 12
Sep 1956 JD-1D A8 (Utility, Aging) 1
Oct 1956 JD-1 AQ (Utility, Not Aging) 1
Oct 1956 JD-1 A8 (Utility, Aging) 11
Oct 1956 JD-1D A8 (Utility, Aging) 2
Nov 1956 JD-1 A8 (Utility, Aging) 12
Nov 1956 JD-1D A8 (Utility, Aging) 2
Dec 1956 JD-1 AQ (Utility, Not-Aging) 1
Dec 1956 JD-1 A8 (Utility, Aging) 10
Dec 1956 JD-1D A8 (Utility, Aging) 3


VU-4 Squadron Count

This table summarizes the total count of the squadron's Invaders each month, regardless of status.

Period JD-1 JD-1D JD-1X JD-1DX Total
Sep 1956 12 1 0 0 13
Oct 1956 12 2 0 0 14
Nov 1956 12 2 0 0 14
Dec 1956 11 3 0 0 14


VU-10

VU-10 was Utility Squadron 10. They were based out of Guantanamo Bay (GITMO).

Period Type Status Number
Sep 1956 JD-1 AQ (Utility, not Aging) 1
Sep 1956 JD-1 A8 (Utility, Aging) 13
Oct 1956 JD-1 AQ (Utility, Not Aging) 2
Oct 1956 JD-1 A8 (Utility, Aging) 12
Nov 1956 JD-1 AQ (Utility, Not Aging) 2
Nov 1956 JD-1 A8 (Utility, Aging) 12
Dec 1956 JD-1 AQ (Utility, Not Aging) 1
Dec 1956 JD-1 A8 (Utility, Aging) 12
Dec 1956 JD-1 F6 (En Route to overhaul, surface transport) 1
Dec 1956 JD-1D A8 (Utility, Aging) 2


VU-10 Squadron Count

This table summarizes the total count of the squadron's Invaders each month, regardless of status.

Period JD-1 JD-1D JD-1X JD-1DX Total
Sep 1956 14 0 0 0 14
Oct 1956 14 0 0 0 14
Nov 1956 14 0 0 0 14
Dec 1956 14 2 0 0 16


NAF Naples

I was honestly surprised to see JD-1s stationed at the base in Italy.


Period Type Status Number
Sep 1956 JD-1 AQ (Utility, not Aging) 1
Sep 1956 JD-1 A8 (Utility, Aging) 3
Oct 1956 JD-1 AQ (Utility, not Aging) 1
Oct 1956 JD-1 A8 (Utility, Aging) 3
Nov 1956 JD-1 AQ (Utility, not Aging) 1
Nov 1956 JD-1 A8 (Utility, Aging) 3
Dec 1956 JD-1 AQ (Utility, not Aging) 1
Dec 1956 JD-1 A8 (Utility, Aging) 3
Dec 1956 JD-1 EJ (Transfer Offsite Overhaul, Flyable) 1


Naples Squadron Count

This table summarizes the total count of the squadron's Invaders each month, regardless of status.

Period JD-1 JD-1D JD-1X JD-1DX Total
Sep 1956 4 0 0 0 4
Oct 1956 4 0 0 0 4
Nov 1956 4 0 0 0 4
Dec 1956 5 0 0 0 5


Atlantic Command Summary

Date VX-2 VU-2 VU-4 VU-10 Naples Total
Sep 1956 2 12 13 14 4 45
Oct 1956 2 12 14 14 4 46
Nov 1956 2 11 14 14 4 45
Dec 1956 2 11 14 16 5 50


Pacific Command (PAC)

VU-1

VU-1 was Utility Squadron 1. They were based out of Barber's Point.

Period Type Status Number
Sep 1956 JD-1 A8 (Utility, Aging) 5
Sep 1956 JD-1 D3 (Progressive Maintenance) 1
Sep 1956 JD-1 F3 (Flying en-route to maintenance) 1
Oct 1956 JD-1 A8 (Utility, Aging) 6
Nov 1956 JD-1 A8 (Utility, Aging) 6
Dec 1956 JD-1 A8 (Utility, Aging) 6


VU-1 Squadron Count

This table summarizes the total count of the squadron's Invaders each month, regardless of status.

Period JD-1 JD-1D JD-1X JD-1DX Total
Sep 1956 7 0 0 0 7
Oct 1956 6 0 0 0 6
Nov 1956 6 0 0 0 6
Dec 1956 6 0 0 0 6


VU-3

VU-3 was Utility Squadron 3. They were based out of Brown Field. In Sep 1956 the squadron shows JD-1Ds as planned for future use, but none are actually present. The months that are skipped were because this unit had no JD-1s on site.

Period Type Status Number
Nov 1956 JD-1D A8 (Utility, Aging) 1
Dec 1956 JD-1D A8 (Utility, Aging) 1


VU-3 Squadron Count

This table summarizes the total count of the squadron's Invaders each month, regardless of status.

Period JD-1 JD-1D JD-1X JD-1DX Total
Nov 1956 0 1 0 0 1
Dec 1956 0 1 0 0 1


VU-5

VU-5 was Utility Squadron 5. They were based out of Atsugi.

Period Type Status Number
Sep 1956 JD-1 AQ (Utility, Not-Aging) 2
Sep 1956 JD-1 A8 (Utility, Aging) 5
Sep 1956 JD-1 D1 (In Overhaul) 4
Sep 1956 JD-1 A8-A (Detachment A) 2
Oct 1956 JD-1 AQ (Utility, Not-Aging) 1
Oct 1956 JD-1 A8 (Utility, Aging) 5
Oct 1956 JD-1 D1 (In Overhaul) 3
Oct 1956 JD-1 A8-A (Detachment A) 3
Nov 1956 JD-1 AQ (Utility, not-Aging) 1
Nov 1956 JD-1 A8 (Utility, Aging) 5
Nov 1956 JD-1 D1 (In Overhaul) 2
Nov 1956 JD-1 A8-A (Detachment A) 3
Dec 1956 JD-1 AQ (Utility, Not-Aging) 1
Dec 1956 JD-1 A8 (Utility, Aging) 5
Dec 1956 JD-1 D1 (In Overhaul) 1
Dec 1956 JD-1 AQ-A (Detachment A) 1
Dec 1956 JD-1 A8-A (Detachment A) 3


VU-5 Squadron Count

This table summarizes the total count of the squadron's Invaders each month, regardless of status.

Period JD-1 JD-1D JD-1X JD-1DX Total
Sep 1956 13 0 0 0 13
Oct 1956 12 0 0 0 12
Nov 1956 11 0 0 0 11
Dec 1956 11 0 0 0 11


VU-7

VU-7 was Utility Squadron 7. They were based out of Brown Field.

Period Type Status Number
Sep 1956 JD-1 AQ (Utility, Not-Aging) 2
Sep 1956 JD-1 A8 (Utility, Aging) 13
Oct 1956 JD-1 AQ (Utility, Not-Aging) 1
Oct 1956 JD-1 A8 (Utility, Aging) 12
Nov 1956 JD-1 AQ (Utility, Not-Aging) 1
Nov 1956 JD-1 A8 (Utility, Aging) 12
Dec 1956 JD-1 AQ (Utility, Not-Aging) 1
Dec 1956 JD-1 A8 (Utility, Aging) 11
Dec 1956 JD-1D A8 (Utility, Aging) 1


VU-7 Squadron Count

This table summarizes the total count of the squadron's Invaders each month, regardless of status.

Period JD-1 JD-1D JD-1X JD-1DX Total
Sep 1956 15 0 0 0 15
Oct 1956 13 0 0 0 13
Nov 1956 13 0 0 0 13
Dec 1956 12 1 0 0 13

NAF Advance Base Oppama

NAF Adv. Base Oppama doesn't show any JD-1s in Sep 1956, but they do report some in Oct 1956. The base appears to be a repair base, based on the status codes being reported.


Period Type Status Number
Oct 1956 JD-1 D1 (In Overhaul) 2
Nov 1956 JD-1 D1 (In Overhaul) 3
Dec 1956 JD-1 D1 (In Overhaul) 3


Oppama Squadron Count

This table summarizes the total count of the squadron's Invaders each month, regardless of status.

Period JD-1 JD-1D JD-1X JD-1DX Total
Oct 1956 2 0 0 0 2
Nov 1956 3 0 0 0 3
Dec 1956 3 0 0 0 3


Pacific Command Summary

Date VU-1 VU-3 VU-5 VU-7 Oppama Total
Sep 1956 7 0 13 15 0 35
Oct 1956 6 0 12 13 2 33
Nov 1956 6 1 11 13 3 34
Dec 1956 6 1 11 13 3 34


Research & Development, BAUER (R&D)

R&D Aircraft

This field doesn't list a location. This field is a NOT a duplicate of other bases within the R&D section as they have different aircraft counts and lists.

Period Type Status Number
Sep 1956 JD-1 A9 (R&D, Aging) 1
Sep 1956 JD-1D A9 (R&D, Aging) 2
Oct 1956 JD-1 A9 (R&D, Aging) 1
Oct 1956 JD-1D A9 (R&D, Aging) 2
Nov 1956 JD-1 A9 (R&D, Aging) 1
Nov 1956 JD-1D A9 (R&D, Aging) 2
Dec 1956 JD-1 A9 (R&D, Aging) 1
Dec 1956 JD-1D A9 (R&D, Aging) 4


R&D Squadron Count

This table summarizes the total count of the squadron's Invaders each month, regardless of status.

Period JD-1 JD-1D JD-1X JD-1DX Total
Sep 1956 1 2 0 0 3
Oct 1956 1 2 0 0 3
Nov 1956 1 2 0 0 3
Dec 1956 1 4 0 0 5


NATC Patuxent River

NATC Pax River is a Naval Air Test Center.

Period Type Status Number
Sep 1956 JD-1 A9 (R&D, Aging) 1
Oct 1956 JD-1 A9 (R&D, Aging) 1
Nov 1956 JD-1 A9 (R&D, Aging) 1
Dec 1956 JD-1 A9 (R&D, Aging) 1


Pax River Squadron Count

This table summarizes the total count of the squadron's Invaders each month, regardless of status.

Period JD-1 JD-1D JD-1X JD-1DX Total
Sep 1956 1 0 0 0 1
Oct 1956 1 0 0 0 1
Nov 1956 1 0 0 0 1
Dec 1956 1 0 0 0 1


NAMTC Point Mugu

Naval Air Missile Test Center Point Mugu was based out of Point Mugu. JD-1s that say "Point Mugu" on the tail were almost certainly assigned to this unit and not the VX squadron stationed there.

Period Type Status Number
Sep 1956 JD-1D AR (R&D, Not-Aging) 2
Oct 1956 JD-1D AR (R&D, Not-Aging) 2
Nov 1956 JD-1D AR (R&D, Not-Aging) 2
Dec 1956 JD-1D AR (R&D, Not-Aging) 2


Point Mugu Squadron Count

This table summarizes the total count of the squadron's Invaders each month, regardless of status.

Period JD-1 JD-1D JD-1X JD-1DX Total
Sep 1956 0 2 0 0 2
Oct 1956 0 2 0 0 2
Nov 1956 0 2 0 0 2
Dec 1956 0 2 0 0 2


Research & Development Command Summary

Date R&D Pax River Pt. Mugu Total
Sep 1956 3 1 2 6
Oct 1956 3 1 2 6
Nov 1956 3 1 2 6
Dec 1956 5 1 2 8


Field Activities, Bureau of Aeronautics (BAUER)

O&R Norfolk

Overhaul & Repair Center Norfolk was a major repair and conversion depot servicing the East Coast.
One of the 4 JD-1Ds with status code B in Sept 1956 is the original XJD-1 Prototype, 57990.

Period Type Status Number
Sep 1956 JD-1 D1 (In Overhaul) 5
Sep 1956 JD-1 E1 (Overhaul in place, Flyable) 1
Sep 1956 JD-1 E6 (Overhaul in place, non-flyable) 1
Sep 1956 JD-1 G6 (Repair) 1
Sep 1956 JD-1X E4 (Overhaul Conversion in place, Flyable) 13
Sep 1956 JD-1D B (Awaiting Assignment) 4
Sep 1956 JD-1DX DD (Overhaul Conversion) 1
Sep 1956 JD-1DX D4 (Conversion) 4
Oct 1956 JD-1 DA (Rework complete, needs flight check) 2
Oct 1956 JD-1 D1 (In Overhaul) 7
Oct 1956 JD-1 E1 (Overhaul in place, Flyable) 1
Oct 1956 JD-1 E6 (Overhaul in place, non-flyable) 1
Oct 1956 JD-1 G6 (Repair) 1
Oct 1956 JD-1X E4 (Overhaul Conversion in place, Flyable) 13
Oct 1956 JD-1DX DD (Overhaul Conversion) 3
Oct 1956 JD-1DX D4 (Conversion) 2
Nov 1956 JD-1 D1 (In Overhaul) 9
Nov 1956 JD-1 E1 (Overhaul in place, Flyable) 2
Oct 1956 JD-1 E6 (Overhaul in place, non-flyable) 1
Nov 1956 JD-1 G5 (Modification) 1
Nov 1956 JD-1X E4 (Overhaul Conversion in place, Flyable) 10
Nov 1956 JD-1D B (Awaiting Assignment) 4
Nov 1956 JD-1DX DD (Overhaul Conversion) 1
Nov 1956 JD-1DX D4 (Conversion) 3
Dec 1956 JD-1 B (Awaiting Assignment) 2
Dec 1956 JD-1 DA (Overhaul Complete, Pending flight check) 2
Dec 1956 JD-1 D1 (Overhaul Complete) 5
Dec 1956 JD-1 E1 (Overhaul onsite, flyable) 3
Dec 1956 JD-1 G5 (Modification) 1
Dec 1956 JD-1X E4 (Overhaul Conversion in place, Flyable) 10
Dec 1956 JD-1D C (En route to base, flying) 1
Dec 1956 JD-1DX D4 (Conversion) 3


Norfolk Squadron Count

This table summarizes the total count of the squadron's Invaders each month, regardless of status.

Period JD-1 JD-1D JD-1X JD-1DX Total
Sep 1956 8 4 13 4 29
Oct 1956 12 0 13 5 30
Nov 1956 12 4 10 4 30
Dec 1956 13 1 10 3 27


O&R Quonset Pt

Overhaul & Repair Center Quonset Point was a major repair and conversion depot servicing the northeast.

Period Type Status Number
Sep 1956 JD-1 EN (Transfer for Rework, Non-flyable) 1


Quonset Point Squadron Count

This table summarizes the total count of the squadron's Invaders each month, regardless of status.

Period JD-1 JD-1D JD-1X JD-1DX Total
Sep 1956 1 0 0 0 1
Oct 1956 0 0 0 0 0
Nov 1956 0 0 0 0 0
Dec 1956 0 0 0 0 0


Litchfield Park

Litchfield Park is a US Navy Storage Facility (aka:Boneyard).

Period Type Status Number
Sep 1956 JD-1 MX (Storage, Rework Req. Not in CANS) 3
Sep 1956 JD-1X M4 (Storage, Conversion Rework Required) 11
Oct 1956 JD-1 MX (Storage, Rework Req. Not in CANS) 2
Oct 1956 JD-1X M4 (Storage, Conversion Rework Required) 11
Nov 1956 JD-1 MX (Storage, Rework Req. Not in CANS) 2
Nov 1956 JD-1X M4 (Storage, Conversion Rework Required) 11
Dec 1956 JD-1 MX (Storage, Rework Req. Not in CANS) 1
Dec 1956 JD-1X M4 (Storage, Conversion Rework Required) 11


Litchfield Park Squadron Count

This table summarizes the total count of the squadron's Invaders each month, regardless of status.

Period JD-1 JD-1D JD-1X JD-1DX Total
Sep 1956 3 0 11 0 14
Oct 1956 2 0 11 0 13
Nov 1956 2 0 11 0 13
Dec 1956 1 0 11 0 12


Bureau of Aeronautics Command Summary

Date Norfolk Quonset Litchfield Total
Sep 1956 29 1 14 44
Oct 1956 30 0 13 43
Nov 1956 30 0 13 43
Dec 1956 27 0 12 39


US Navy Total Summary

Preliminary thoughts regarding the table below. We know from the Bureau Number list that the US Navy had 150 JD-1s and 2 XJD-1s in total. The XJD-1s began service life with the Navy in March 1946. By the time time this report was started in Sep 1956 a decade has already passed. In that period 20 JD-1s are unaccounted for. At this time I do not know if they were destroyed in an accident or simply scrapped. As I get the individual aircraft records this will become clear. What is clear is that since none of the JD-1s were used in combat, none of the JD-1s were lost due to enemy action.

Date Atlantic Pacific R&D BAUER Total
Sep 1956 45 35 6 44 130
Oct 1956 46 33 6 43 128
Nov 1956 45 34 6 43 128
Dec 1956 50 34 8 39 131


Understanding the Inventory Codes

All of the Allowances Reports use an alphanumeric code system to distinguish the status of the aircraft. I have abbreviated the codes in the tables above, but here I will provide additional explanations.

Status Code Definition Comments
A2 Combat Services According to what I've been able to find, the Combat Services role deals primarily with transporting of goods or equipment into combat zones to support the combat personnel embroiled in the fight. I do know that several Invaders were modified in Africa to carry cargo pallets or fitted with seat pallets to serve as emergency transports, so its possible the JD-1s in this role could have been put to use along the same lines. I'll keep digging into this.
A8 Utility, Aging Planes in the utility role were assigned to be target tugs or to act as air targets to be intercepted.
A9 Research & Development
AK Combat Services, Not Aging
AQ Utility, Not Aging
AR R&D, Not-Aging.
B Awaiting Assignment This unit is usually Fully Mission Capable (FMC), but not assigned to a unit.
C en route, flying The plane is being moved by air to another location, usually an overhaul & repair depot.
C9 en route, surface The plane has been loaded on a carrier and is being transported via sea to another location.
D1 In Overhaul Usually engine changes and maintenance of that sort.
D2 Progressive Maintenance, Conversion Combines Progressive maintenance with conversion to a different type, such as a JD-1 to a JD-1D, for example.
D3 Progressive Maintenance
D4 Overhaul Conversion Combines overhaul with conversion to a different type, such as JD-1 to JD-1D, for example.
DA Overhaul Complete except for flight check.
DB Progressive Maintenance conversion complete except for flight check
DC Progressive Maintenance Complete except for flight check
DD Overhaul conversion complete except for flight check
E1 To be overhauled where located, flyable
E2 To have progressive maintenance conversion where located, flyable
E3 To have progressive maintenance where located, flyable.
E4 To have overhaul conversion where located, flyable.
E6 To be overhauled where located, not flyable
E7 To have progressive maintenance conversion where located, not flyable
E8 To have overhaul conversion where located, not flyable.
E9 To have overhaul conversion where located, not flyable.
EJ To be overhauled elsewhere, flyable
EK To have progressive maintenance conversion elsewhere, flyable
EL To have progressive maintenance elsewhere, flyable.
EM To have overhaul conversion elsewhere, flyable.
EN To be overhauled elsewhere, not flyable
EP To have progressive maintenance conversion where located, not flyable
EQ To have overhaul conversion elsewhere, not flyable.
ER To have overhaul conversion elsewhere, not flyable.
F En route to rework This code is incomplete, but sometimes used. It should be followed with a number
F1 En route for overhaul, flying
F2 en route to progressive maintenance conversion, flying
F3 en route to progressive maintenance, flying.
F4 en route to overhaul conversion, flying.
F6 en route tp overhaul, surface (Sea) transport
F7 en route to progressive maintenance conversion, surface (Sea) transport
F8 en route to overhaul conversion, surface (Sea) transport
F9 en route to overhaul conversion, surface (Sea) transport
G4 Conversion Conversion to a different type of plane.
G5 Modification
G6 Repair As the result from an accident.
G7 Modernization
G8 Modernization conversion
MX In storage-standard rework required, not in containers The aircraft is parked in one piece.
MY In storage-standard rework not required, not in containers the aircraft is parked in one piece.
Q1 Awaiting strike decision, damage
P2 Awaiting strike decision, depreciation, flyable
P3 awaiting strike decision, administrative, flyable.
P4 awaiting strike decision, Service life ended, flyable
RD struck while in process of standard rework.


Aging vs Non-Aging

Aircraft Non-Aging Record (OPNAV 4790/18)

The Aircraft Non-Aging Record is maintained as a part of the aircraft logbook to provide a permanent record of time accumulated in nonaging situations. To understand the purpose and use of this record, you must understand what is meant by aircraft aging and nonaging.

When an aircraft is purchased by the Navy, the Navy plans to operate the aircraft for a specified number of months, called operational service months (OPSERMOS). The total number of OPSERMOS expected before the aircraft is retired is the operational service life or planned service life of the aircraft. For example, an aircraft is purchased by the Navy with a planned service life of 60 OPSERMOS. This means 60 months of actual operational use. The days during which this aircraft is in storage, undergoing special rework at the depot facility, etc., do not count toward the planned service life of the aircraft; they are nonaging days. A properly maintained nonaging record in the logbook provides a record of all time periods that the aircraft was not aging, and will ultimately aid in the aircraft receiving its full operational service life.

The dates entered in block 6 of the nonaging record reflect the entire period the aircraft is out of service, including all transit, awaiting, and in-process time (pipeline).

The accumulative nonaging days are recorded in block 8. If an entry exceeds 30, or a multiple thereof, record 30, 60, 90, etc., in block 8 and the excess in block 9. Whenever 30, 60, 90, etc., is entered in block 8, an OPNAV XRAY is forwarded to modify the period end date 1 month for each 30-day increment. After the OPNAV XRAY report, the accumulated days in block 8 are reduced to zero. The next entry in block 8 will include the total in block 9 from prior incidents.

NOTE: Not mission capable (NMC) or partial mission capable (PMC) time is NOT recorded on the nonaging record.

Retrieved from "http://claybornglobal.com/IHF/index.php?title=Navy_Inventory_Records&oldid=8751"