Cool coincidence. In a past job, I specifically made replacement PCMCIA cards for these (and other) planes. Instead of making cards with a controller and onboard storage, we made cards with an FPGA/microcontroller and a microSD card soldered to the PCB. We did this specifically because these aircraft use (at least partially) broken implementations of the PCMCIA protocol, and we'd update the bus protocol per aircraft to work around the limitations. None of these planes can just go buy stuff off the street because some large portion just doesn't work because their protocol isn't fully implemented and isn't flexible to deal with variance in timing/speed/etc.
A fun story: Our cards had whatever industrial-spec microSD card we could find (16GB, 32GB, etc.), and we'd internally limit the disk size to whatever the platform needed. Almost every aircraft had some specific number of MB they wanted because all of their CONOPS listed it, and they didn't want to update documentation or software to put a different number there. We had a plane that could only use EXACTLY 128MB, but they were currently using 256MB cards and partitioning them to 128MB. We updated the disk size to present as 128MB so they could skip this step, and they specifically told us to put it back to 256MB because they didn't want to update the commissioning process to remove the partitioning step.
It was rewarding work, and the card we designed was cheap (~$500 each, which is literally nothing for major platforms like this) and 100% US-designed and made (with the exception of ICs manufactured in the usual places). Still, the procedural and cultural practices of these program offices made it a real struggle to get traction and deploy them widely. Government acquisition is just generally designed around funding primes for current development and then paying through the nose for sustainment later. It was hard to design something for widespread sustainment use because by the time you were done and ready for production, a bunch of parts would be obsolete. Then you'd have to rev the design over and over. We were never allowed to stockpile anything, even if it was trivially cheap, to facilitate production later.
Without going into a ton of detail, I was working as a federal employee for a federal laboratory. Per regulation we couldn't purchase anything not directly tied to an agreement, and we weren't allowed to complete with industry.
Typical work would look like this:
A group would come to us and say, "We use these cards, but they wear out and we need like 200 more to keep running for 15 more years, we talked to primes about fixing this problem for us but they said the only thing they're willing to do is redesign the entire data handling infrastructure in the plane for $500M." So we'd get some tiny amount of money (like $200k) and redesign the card and make them ~20 prototypes. It'd work great, then they'd spend 3 years working on production contracts to try to get 200 built for $100k. In 3 years, some part would go obsolete, they'd come back and give us $50k to update the design and test, then start the 3 years cycle to buy 200 again. Rinse and repeat.
If they would have just given us like $30k, we already knew which parts were high risk of going obsolete, we could have just bought everything necessary to build 1000 units and dropped them in storage, but federal regulation limited what was possible. SUPER frustrating to have something that solves a problem and watch it fall apart over crappy policy.
It's sad to see this request, knowing that I was part of the team that designed a solution specifically to solve it, knowing it worked and tested it on the platform, but some part probably went obsolete and they never got enough manufactured to solve the problem permanently.
Sounds like an opportunity. Form "Jotux Electronic Supply, LLC" (JES) and stockpile the stuff that's cheap now but you believe is gong to be unavailable in the future. When they come back in a few years, the parts are available from JES, they are just much more expensive now.
This was a regular and consistent joke we made, and we saw contractors do specifically this as well. All of our work was intended to be advertised and eventually produced by multiple manufacturing contractors. One contractor would see that a specific part was going obsolete and go buy all of them, and basically starve out the competition. After they were the only contractor that could actually build it the price they would quote would go up 10x.
That's because it is. The FAR is trash and should be thrown out and re-written, but congress isn't operational enough to do it and primes have plowed too many regulations into it to ever let them give it up.
In my experience, trying to get the government to adopt innovation feels cumbersome and "paperwork-first." I've brought disruptive tech to some FedCiv orgs and they would say things like "we don't have a line item for that in our budget." Luckily, things like OTAs signal an attempt on their part to make the process better. (I'd recommend the book Unit X by Raj M. Shah for a history behind the push to improve the acquisition process).
they didn't want to update the commissioning process to remove the partitioning step
Depending on regulations, updating the processes and associated documentation might have been more wasteful with regards to time to update, review and update the processes, time to get everyone retrained, risks of being out of compliance due to confusion, materials to print everything out, etc.
Yes, 100% agree. Another common problem we saw was that most major systems were owned by one specific contractor. Lockheed owns f-22, Boeing owns f-15, etc. Oftentimes there was some requirement to use the process as defined and delivered from the contractor. Want to update a document to remove step 7 from the data loading process? Welp, you'll need to get them on contract to update the document, verify it, regenerated documentation, train users to stop doing step 7, and reissue to the PO. That will only be $1.5M.
I'm not saying it's bad that these processes are in place, they make sense for systems this large, expensive, complicated and important. But there once was a time where government employees owned a bunch of this and when there was a problem they could just go fix it. That has been eroded, and prime contractor dependency has been enshrined in the way we purchase and maintain these systems with the sole intent of giving more money to those contractors.
This is more of a survey to identify _potential_ suppliers of NEW CF/PC memory cards. It's not a request for bids, nor asking civilians to root around their junk drawers for cards to send off to the military.
Reading between the lines, they are likely evaluating multiple options for modernizing whatever F-22 system this is, and need to find out if going this route is even feasible.
Good catch. This is typically "market research" by the agencies and departments performing it. Many outcomes possible, such as a BPA, an IDIQ, a sole source supplier, etc.
The capability of the plane is to fly and blow stuff up. Modernizing some internal component adds nothing to its capabilities and introduces more risk that something will go wrong, possibly even in flight. Therefore, they should stay with the standards that work.
> Sandisk Corporation (formerly SunDisk Corporation and SanDisk Corporation) is an American multinational computer semiconductor company based in Milpitas, California.
It's worth pointing out that there are actually two main types of PCMCIA memory cards. The most common by far are the ATA cards mentioned here, which are basically CF cards in a different form factor (equivalent to a CF card in a CF-to-PCMCIA adapter) and work by emulating either an IDE hard drive or an ISA IDE controller depending on wiring. While uncommon at this point, CF controller chips are still available and some specialized suppliers do manufacture these cards brand new using modern NAND flash.
The much more problematic ones to find a replacement for in 2026 are the so-called "linear" memory-mapped cards, consisting of one or more banks of raw parallel NOR flash with no controller IC. Linear cards were never standardized and the protocol used to interface to parallel flash can vary greatly across chip families, so the vast majority of devices that use them are hardcoded to only accept cards with a specific manufacturer and device ID. Many NOR flash manufacturers from the turn of the century have long discontinued their products and emulating parallel flash using modern FPGAs and microcontrollers is also non-trivial due to their memory-mapped nature, so owners of legacy telecom equipment and original Dance Dance Revolution arcade cabinets [1] are left with pretty much no viable replacement option once the stock cards fail.
All current US military aircraft (at least up through the F-35) use CF cards to take mission planning from the laptops in the SCIF (or whatever unclass space they are using) to the aircraft.
As an aside, LCACs (among other platforms) also use these systems and cards. So this is a pretty widespread use case.
Bought a few CF cards from Dogfish SSD (https://dogfishssd.com/) sometime ago. They are readily available on Amazon and can be bought with relatively no fuss. The company are NOT based out of the US though.
The company that I do recommend for any industrial flash is Delkin Devices (https://www.delkindevices.com/). They are based out of San Diego, CA and I bought USB 3.0 high endurance drives from them and so far the performance of those have been solid, and it's lasted me many cycles. These are whom you'd be in contact with, for bids like these.
It's worth expanding the supply chain options locally. If anyone needs this they'd have to get Micron or Sandisk to make and assemble them into other form factors. This part is what is harder than it looks, and would need to be done.
As a bit of a fun aside, Industrial CF cards are a popular stand-in for hard disks in vintage computers (since in IDE mode they can be adapted passively to IDE - they're both parallel ATA but with different pinouts). Too bad they don't make hard drive noises, though.
As I recall, there was a period of time where pro photographers would purchase MP3 players that used the microdrives and strip the drive out because it was significantly cheaper than buying the photog marketed microdrive alone.
The 2004 iPod Photo (classic iPod with an upgraded color display) also had a "camera connector" designed to let you dump photos from a camera to its more spacious hard drive.
I forgot how much an indicator hard drive noises were until just now, in those days where programs took 2 mins to either open or crash. Frozen ui but plenty of hdd noise indicating read write, probably a good sign it hasn’t actually crashed and you just need to sit tight.
True, but a frozen system with high disk activity could also indicate that the app had a memory leak and was simply dumping glitchy data into a growing scratch file/partition after it exhausted available ram.
"[...] The PC or CF card must have a storage capacity of 256 megabytes (MB) or greater [...]" I'm guessing they have some system that bootstraps off of PC cards, or stores some small amount of low-bandwidth essential things. It's interesting that it's cheaper to req. a bunch of cards & adapters than it is to retrofit & modernize. Well, I suppose that's not that surprising, if I stop to think about it; from a systems integration point it's certainly way more reliable and less risky to replace a like part for a like part, rather than redesigning the hardware to use a more modern flash storage device.
You'd be _amazed_ at the red tape and expense required to modernize any part of a military aircraft maintenance system. You have to understand, when the US military orders a new plane, they don't buy only the plane. They buy the blueprints, parts manifest, pilot training curriculum, maintenance manuals, maintenance equipment, etc... literally just about everything except the manufacturing facility where they are built. Each aircraft is its own big program with tens of thousands of people employed by it at any given time. Changing even one small piece of it is a monumental undertaking.
Circa 2000, I worked in an avionics shop that serviced (among others) MH-53J helicopter navigation and autopilot systems. The test bench for this system was about 20-feet long end-to-end and was driven by a rack-mount IBM PC with an 8086 running MS-DOS. Storage was a 5MB (or so) pre-IDE hard drive with its own controller. These were... not reliable. And since we were a training base, getting new ones was just about impossible. When the drive died, much of the test bench was useless. I wanted so bad to swap out that drive with some kind of ISA->CompactFlash adapter, but _any_ unauthorized modifications to a test bench or procedure were strictly illegal, even if you knew what you're doing.
China again is the gate to the bridge from 20th to 21st century. We don't have them because we never even tried to secure the supply chain beyond the bare minimum.
Or, you could halt the data center plague, causing the storage prices to plummet, and then buy normal modern storage at normal prices again. Because you have that power. You're literally part of the US government.
These are legacy systems using legacy storage that almost no one produces or sells anymore. It's completely unrelated to current memory/storage pricing or shortages.
A fun story: Our cards had whatever industrial-spec microSD card we could find (16GB, 32GB, etc.), and we'd internally limit the disk size to whatever the platform needed. Almost every aircraft had some specific number of MB they wanted because all of their CONOPS listed it, and they didn't want to update documentation or software to put a different number there. We had a plane that could only use EXACTLY 128MB, but they were currently using 256MB cards and partitioning them to 128MB. We updated the disk size to present as 128MB so they could skip this step, and they specifically told us to put it back to 256MB because they didn't want to update the commissioning process to remove the partitioning step.
It was rewarding work, and the card we designed was cheap (~$500 each, which is literally nothing for major platforms like this) and 100% US-designed and made (with the exception of ICs manufactured in the usual places). Still, the procedural and cultural practices of these program offices made it a real struggle to get traction and deploy them widely. Government acquisition is just generally designed around funding primes for current development and then paying through the nose for sustainment later. It was hard to design something for widespread sustainment use because by the time you were done and ready for production, a bunch of parts would be obsolete. Then you'd have to rev the design over and over. We were never allowed to stockpile anything, even if it was trivially cheap, to facilitate production later.
Now allowed by whom? Was it a business decision or a regulation?
Typical work would look like this:
A group would come to us and say, "We use these cards, but they wear out and we need like 200 more to keep running for 15 more years, we talked to primes about fixing this problem for us but they said the only thing they're willing to do is redesign the entire data handling infrastructure in the plane for $500M." So we'd get some tiny amount of money (like $200k) and redesign the card and make them ~20 prototypes. It'd work great, then they'd spend 3 years working on production contracts to try to get 200 built for $100k. In 3 years, some part would go obsolete, they'd come back and give us $50k to update the design and test, then start the 3 years cycle to buy 200 again. Rinse and repeat.
If they would have just given us like $30k, we already knew which parts were high risk of going obsolete, we could have just bought everything necessary to build 1000 units and dropped them in storage, but federal regulation limited what was possible. SUPER frustrating to have something that solves a problem and watch it fall apart over crappy policy.
It's sad to see this request, knowing that I was part of the team that designed a solution specifically to solve it, knowing it worked and tested it on the platform, but some part probably went obsolete and they never got enough manufactured to solve the problem permanently.
Wasteful here is relative. Wasteful relative to what? Certainly not wasteful relative to upgrading all the existing hardware to take microsd cards
Depending on regulations, updating the processes and associated documentation might have been more wasteful with regards to time to update, review and update the processes, time to get everyone retrained, risks of being out of compliance due to confusion, materials to print everything out, etc.
I'm not saying it's bad that these processes are in place, they make sense for systems this large, expensive, complicated and important. But there once was a time where government employees owned a bunch of this and when there was a problem they could just go fix it. That has been eroded, and prime contractor dependency has been enshrined in the way we purchase and maintain these systems with the sole intent of giving more money to those contractors.
Pure regulatory capture: https://en.wikipedia.org/wiki/Regulatory_capture
This is more of a survey to identify _potential_ suppliers of NEW CF/PC memory cards. It's not a request for bids, nor asking civilians to root around their junk drawers for cards to send off to the military.
Reading between the lines, they are likely evaluating multiple options for modernizing whatever F-22 system this is, and need to find out if going this route is even feasible.
"Otherwise please use the original title, unless it is misleading or linkbait; don't editorialize."
https://news.ycombinator.com/newsguidelines.html
They'll probably want SanDisk extreme for a super sonic jet fighter though and that's pricier.
https://en.wikipedia.org/wiki/Sandisk
The much more problematic ones to find a replacement for in 2026 are the so-called "linear" memory-mapped cards, consisting of one or more banks of raw parallel NOR flash with no controller IC. Linear cards were never standardized and the protocol used to interface to parallel flash can vary greatly across chip families, so the vast majority of devices that use them are hardcoded to only accept cards with a specific manufacturer and device ID. Many NOR flash manufacturers from the turn of the century have long discontinued their products and emulating parallel flash using modern FPGAs and microcontrollers is also non-trivial due to their memory-mapped nature, so owners of legacy telecom equipment and original Dance Dance Revolution arcade cabinets [1] are left with pretty much no viable replacement option once the stock cards fail.
[1] https://psx-spx.consoledev.net/konamisystem573/#flash-chips-...
All current US military aircraft (at least up through the F-35) use CF cards to take mission planning from the laptops in the SCIF (or whatever unclass space they are using) to the aircraft.
As an aside, LCACs (among other platforms) also use these systems and cards. So this is a pretty widespread use case.
The company that I do recommend for any industrial flash is Delkin Devices (https://www.delkindevices.com/). They are based out of San Diego, CA and I bought USB 3.0 high endurance drives from them and so far the performance of those have been solid, and it's lasted me many cycles. These are whom you'd be in contact with, for bids like these.
It's worth expanding the supply chain options locally. If anyone needs this they'd have to get Micron or Sandisk to make and assemble them into other form factors. This part is what is harder than it looks, and would need to be done.
Funny thing, there were CF cards which were basically mini hard drives
https://en.wikipedia.org/wiki/Microdrive
They were very popular with professional photographers before that.
Circa 2000, I worked in an avionics shop that serviced (among others) MH-53J helicopter navigation and autopilot systems. The test bench for this system was about 20-feet long end-to-end and was driven by a rack-mount IBM PC with an 8086 running MS-DOS. Storage was a 5MB (or so) pre-IDE hard drive with its own controller. These were... not reliable. And since we were a training base, getting new ones was just about impossible. When the drive died, much of the test bench was useless. I wanted so bad to swap out that drive with some kind of ISA->CompactFlash adapter, but _any_ unauthorized modifications to a test bench or procedure were strictly illegal, even if you knew what you're doing.
One extra layer, but the chips are commodity.
With glue, should be able to meet environmentals, shock and vibe etc