<?xml version="1.0" encoding="UTF-8"?>
 <rdf:RDF xmlns="http://purl.org/rss/1.0/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:cc="http://web.resource.org/cc/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/">
  <channel rdf:about="http://pinboard.in">
    <title>Pinboard (jm)</title>
    <link>https://pinboard.in/u:jm/public/</link>
    <description>recent bookmarks from jm</description>
    <items>
      <rdf:Seq>	<rdf:li rdf:resource="https://99percentinvisible.org/episode/children-of-the-magenta-automation-paradox-pt-1/"/>
	<rdf:li rdf:resource="https://leehamnews.com/2024/01/15/unplanned-removal-installation-inspection-procedure-at-boeing/#comment-509962"/>
	<rdf:li rdf:resource="https://www.theguardian.com/world/2021/apr/09/tui-plane-serious-incident-every-miss-on-board-child-weight-birmingham-majorca?CMP=Share_AndroidApp_Other"/>
	<rdf:li rdf:resource="https://www.aviationreg.ie/_fileupload/Image/Regulation%20EC261%202004.pdf"/>
	<rdf:li rdf:resource="https://www.seattletimes.com/business/boeing-aerospace/failed-certification-faa-missed-safety-issues-in-the-737-max-system-implicated-in-the-lion-air-crash/"/>
	<rdf:li rdf:resource="https://www.flightrights.ie/"/>
	<rdf:li rdf:resource="http://www.popularmechanics.com/technology/aviation/crashes/what-really-happened-aboard-air-france-447-6611877"/>
	<rdf:li rdf:resource="https://plus.google.com/u/0/110897184785831382163/posts/5qsNxFEaiML"/>
	<rdf:li rdf:resource="http://blog.runwayfinder.com/"/>
	<rdf:li rdf:resource="http://ithurtstonotbreathe.blogspot.com/2009/08/socializing-weather.html"/>
      </rdf:Seq>
    </items>
  </channel><item rdf:about="https://99percentinvisible.org/episode/children-of-the-magenta-automation-paradox-pt-1/">
    <title>Modal interfaces considered harmful</title>
    <dc:date>2024-09-19T13:13:11+00:00</dc:date>
    <link>https://99percentinvisible.org/episode/children-of-the-magenta-automation-paradox-pt-1/</link>
    <dc:creator>jm</dc:creator><description><![CDATA[A great line from the 99 Percent Invisible episode titled "Children of the Magenta (Automation Paradox, pt. 1)", regarding the Air France flight 447 disaster:

<blockquote>When one of the co-pilots hauled back on his stick, he pitched the plane into an angle that eventually caused the stall. [...] it’s possible that he didn’t understand that he was now flying in a different mode, one which would not regulate and smooth out his movements. This confusion about what how the fly-by-wire system responds in different modes is referred to, aptly, as “mode confusion,”  and it has come up in other accidents.</blockquote>

]]></description>
<dc:subject>automation aviation flying modal-interfaces ui ux interfaces modes mode-confusion air-france-447 disasters</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:464d3b2a60c7/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:automation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:aviation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:flying"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:modal-interfaces"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:ui"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:ux"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:interfaces"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:modes"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:mode-confusion"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:air-france-447"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:disasters"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://leehamnews.com/2024/01/15/unplanned-removal-installation-inspection-procedure-at-boeing/#comment-509962">
    <title>&quot;In Boeing production speak, this is a “process failure”. For an A&amp;P mechanic at an airline, this would be called “federal crime”.&quot;</title>
    <dc:date>2024-01-24T11:23:43+00:00</dc:date>
    <link>https://leehamnews.com/2024/01/15/unplanned-removal-installation-inspection-procedure-at-boeing/#comment-509962</link>
    <dc:creator>jm</dc:creator><description><![CDATA[This may be the greatest leak ever left as a comment on a newspaper article, from a Boeing employee on an article at the Leeham News entitled _“Unplanned” removal, installation inspection procedure at Boeing_.  Enjoy!

<blockquote>
Current Boeing employee here – I will save you waiting two years for the NTSB report to come out and give it to you for free: the reason the door blew off is stated in black and white in Boeings own records. It is also very, very stupid and speaks volumes about the quality culture at certain portions of the business.

A couple of things to cover before we begin:

Q1) Why should we believe you?
A) You shouldn’t, I’m some random throwaway account, do your own due diligence. Others who work at Boeing can verify what I say is true, but all I ask is you consider the following based on its own merits.

Q2) Why are you doing this?
A) Because there are many cultures at Boeing, and while the executive culture may be throughly compromised since we were bought by McD, there are many other people who still push for a quality product with cutting edge design. My hope is that this is the wake up call that finally forces the Board to take decisive action, and remove the executives that are resisting the necessary cultural changes to return to a company that values safety and quality above schedule.

With that out of the way… why did the left hand (LH) mid-exit door plug blow off of the 737-9 registered as N704AL? Simple- as has been covered in a number of articles and videos across aviation channels, there are 4 bolts that prevent the mid-exit door plug from sliding up off of the door stop fittings that take the actual pressurization loads in flight, and these 4 bolts were not installed when Boeing delivered the airplane, our own records reflect this.

The mid-exit doors on a 737-9 of both the regular and plug variety come from Spirit already installed in what is supposed to be the final configuration and in the Renton factory, there is a job for the doors team to verify this “final” install and rigging meets drawing requirements. In a healthy production system, this would be a “belt and suspenders” sort of check, but the 737 production system is quite far from healthy, its a rambling, shambling, disaster waiting to happen. As a result, this check job that should find minimal defects has in the past 365 calendar days recorded 392 nonconforming findings on 737 mid fuselage door installations (so both actual doors for the high density configs, and plugs like the one that blew out). That is a hideously high and very alarming number, and if our quality system on 737 was healthy, it would have stopped the line and driven the issue back to supplier after the first few instances. Obviously, this did not happen. Now, on the incident aircraft this check job was completed on 31 August 2023, and did turn up discrepancies, but on the RH side door, not the LH that actually failed. I could blame the team for missing certain details, but given the enormous volume of defects they were already finding and fixing, it was inevitable something would slip through- and on the incident aircraft something did. I know what you are thinking at this point, but grab some popcorn because there is a plot twist coming up.

The next day on 1 September 2023 a different team (remember 737s flow through the factory quite quickly, 24 hours completely changes who is working on the plane) wrote up a finding for damaged and improperly installed rivets on the LH mid-exit door of the incident aircraft.

A brief aside to explain two of the record systems Boeing uses in production. The first is a program called CMES which stands for something boring and unimportant but what is important is that CMES is the sole authoritative repository for airplane build records (except on 787 which uses a different program). If a build record in CMES says something was built, inspected, and stamped in accordance with the drawing, then the airplane damn well better be per drawing. The second is a program called SAT, which also stands for something boring and unimportant but what is important is that SAT is *not* an authoritative records system, its a bullentin board where various things affecting the airplane build get posted about and updated with resolutions. You can think of it sort of like a idiots version of Slack or something. Wise readers will already be shuddering and wondering how many consultants were involved, because, yes SAT is a *management visibilty tool*. Like any good management visibilty tool, SAT can generate metrics, lots of metrics, and oh God do Boeing managers love their metrics. As a result, SAT postings are the primary topic of discussion at most daily status meetings, and the whole system is perceived as being extremely important despite, I reiterate, it holding no actual authority at all.

We now return to our incident aircraft, which was written up for having defective rivets on the LH mid-exit door. Now as is standard practice kn Renton (but not to my knowledge in Everett on wide bodies) this write-up happened in two forms, one in CMES, which is the correct venue, and once in SAT to “coordinate the response” but really as a behind-covering measure so the manager of the team that wrote it can show his boss he’s shoved the problem onto someone else. Because there are so many problems with the Spirit build in the 737, Spirit has teams on site in Renton performing warranty work for all of their shoddy quality, and this SAT promptly gets shunted into their queue as a warranty item. Lots of bickering ensues in the SAT messages, and it takes a bit for Spirit to get to the work package. Once they have finished, they send it back to a Boeing QA for final acceptance, but then Malicious Stupid Happens! The Boeing QA writes another record in CMES (again, the correct venue) stating (with pictures) that Spirit has not actually reworked the discrepant rivets, they *just painted over the defects*. In Boeing production speak, this is a “process failure”. For an A&P mechanic at an airline, this would be called “federal crime”.

Presented with evidence of their malfeasance, Spirit reopens the package and admits that not only did they not rework the rivets properly, there is a damaged pressure seal they need to replace (who damaged it, and when it was damaged is not clear to me). The big deal with this seal, at least according to frantic SAT postings, is the part is not on hand, and will need to be ordered, which is going to impact schedule, and (reading between the lines here) Management is Not Happy.

However, more critical for purposes of the accident investigation, the pressure seal is unsurprisingly sandwiched between the plug and the fuselage, and you cannot replace it without opening the door plug to gain access. All of this conversation is documented in increasingly aggressive posts in the SAT, but finally we get to the damning entry which reads something along the lines of “coordinating with the doors team to determine if the door will have to be removed entirely, or just opened. If it is removed then a Removal will have to be written.” Note: a Removal is a type of record in CMES that requires formal sign off from QA that the airplane been restored to drawing requirements.

If you have been paying attention to this situation closely, you may be able to spot the critical error: regardless of whether the door is simply opened or removed entirely, the 4 retaining bolts that keep it from sliding off of the door stops have to be pulled out. A removal should be written in either case for QA to verify install, but as it turns out, someone (exactly who will be a fun question for investigators) decides that the door only needs to be opened, and no formal Removal is generated in CMES (the reason for which is unclear, and a major process failure). Therefore, in the official build records of the airplane, a pressure seal that cannot be accessed without opening the door (and thereby removing retaining bolts) is documented as being replaced, but the door is never officially opened and thus no QA inspection is required.

This entire sequence is documented in the SAT, and the nonconformance records in CMES address the damaged rivets and pressure seal, but at no point is the verification job reopened, or is any record of removed retention bolts created, despite it this being a physical impossibility. Finally with Spirit completing their work to Boeing QAs satisfaction, the two rivet-related records in CMES are stamped complete, and the SAT closed on 19 September 2023. No record or comment regarding the retention bolts is made.

I told you it was stupid.

So, where are the bolts? Probably sitting forgotten and unlabeled (because there is no formal record number to label them with) on a work-in-progress bench, unless someone already tossed them in the scrap bin to tidy up.

There’s lots more to be said about the culture that enabled this to happened, but thats the basic details of what happened, the NTSB report will say it in more elegant terms in a few years.
</blockquote>]]></description>
<dc:subject>737max aviation boeing comments throwaway fail qa bolts ntsb</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:7d69f3234f00/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:737max"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:aviation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:boeing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:comments"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:throwaway"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:fail"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:qa"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:bolts"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:ntsb"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.theguardian.com/world/2021/apr/09/tui-plane-serious-incident-every-miss-on-board-child-weight-birmingham-majorca?CMP=Share_AndroidApp_Other">
    <title>Tui plane in ‘serious incident’ due to software bug</title>
    <dc:date>2021-04-09T08:21:32+00:00</dc:date>
    <link>https://www.theguardian.com/world/2021/apr/09/tui-plane-serious-incident-every-miss-on-board-child-weight-birmingham-majorca?CMP=Share_AndroidApp_Other</link>
    <dc:creator>jm</dc:creator><description><![CDATA[Holy cow this could have been pretty serious:

<blockquote>A software mistake caused a Tui flight to take off heavier than expected as female passengers using the title “Miss” were classified as children, an investigation has found.

The departure from Birmingham airport to Majorca with 187 passengers on board was described as a “serious incident” by the Air Accidents Investigation Branch (AAIB).

An update to the airline’s reservation system while its planes were grounded due to the coronavirus pandemic led to 38 passengers on the flight being allocated a child’s “standard weight” of 35kg as opposed to the adult figure of 69kg.  This caused the load sheet – produced for the captain to calculate what inputs are needed for take-off – to state that the Boeing 737 was more than 1,200kg lighter than it actually was.</blockquote>

]]></description>
<dc:subject>flight aviation bugs risks software flying tui titles i18n</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:fc94152fdea8/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:flight"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:aviation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:bugs"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:risks"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:software"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:flying"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:tui"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:titles"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:i18n"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.aviationreg.ie/_fileupload/Image/Regulation%20EC261%202004.pdf">
    <title>EC regulations regarding cancelled flights</title>
    <dc:date>2020-04-01T09:02:36+00:00</dc:date>
    <link>https://www.aviationreg.ie/_fileupload/Image/Regulation%20EC261%202004.pdf</link>
    <dc:creator>jm</dc:creator><description><![CDATA['REGULATION (EC) No 261/2004 OF THE EUROPEAN PARLIAMENT AND OF THE COUNCIL of 11 February 2004, establishing common rules on compensation and assistance to passengers in the event of denied boarding and of cancellation or long delay of flights, and repealing Regulation (EEC) No 295/91'

This may be handy in the coming months I suspect.]]></description>
<dc:subject>aviation flights holidays cancellation consumer-rights consumer ec eu</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:ebb6d4ae1889/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:aviation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:flights"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:holidays"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:cancellation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:consumer-rights"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:consumer"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:ec"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:eu"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.seattletimes.com/business/boeing-aerospace/failed-certification-faa-missed-safety-issues-in-the-737-max-system-implicated-in-the-lion-air-crash/">
    <title>Flawed analysis, failed oversight: How Boeing, FAA certified the suspect 737 MAX flight control system</title>
    <dc:date>2019-03-18T21:21:11+00:00</dc:date>
    <link>https://www.seattletimes.com/business/boeing-aerospace/failed-certification-faa-missed-safety-issues-in-the-737-max-system-implicated-in-the-lion-air-crash/</link>
    <dc:creator>jm</dc:creator><description><![CDATA[omg this article is absolutely horrific.  Boeing are in deep shit if this is borne out.

<blockquote>Like all 737s, the MAX actually has two of the sensors, one on each side of the fuselage near the cockpit. But the MCAS was designed to take a reading from only one of them.

Lemme said Boeing could have designed the system to compare the readings from the two vanes, which would have indicated if one of them was way off.  Alternatively, the system could have been designed to check that the angle-of-attack reading was accurate while the plane was taxiing on the ground before takeoff, when the angle of attack should read zero.

“They could have designed a two-channel system. Or they could have tested the value of angle of attack on the ground,” said Lemme. “I don’t know why they didn’t.”

The black box data provided in the preliminary investigation report shows that readings from the two sensors differed by some 20 degrees not only throughout the flight but also while the airplane taxied on the ground before takeoff.</blockquote>

]]></description>
<dc:subject>faa aviation boeing 737max safety fail sensors flight crashes mcas</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:3452ca238a6b/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:faa"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:aviation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:boeing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:737max"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:safety"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:fail"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:sensors"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:flight"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:crashes"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:mcas"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.flightrights.ie/">
    <title>Flight Rights</title>
    <dc:date>2018-07-11T13:27:45+00:00</dc:date>
    <link>https://www.flightrights.ie/</link>
    <dc:creator>jm</dc:creator><description><![CDATA['This website has been designed to help you, the passenger, understand your rights and entitlements in the event that your air travel plans are disrupted.' from the Commission for Aviation Regulation.  See also thread from Sinead Ryan at https://twitter.com/sinead_ryan/status/1016628694427885568]]></description>
<dc:subject>consumer aviation flights ryanair aer-lingus ireland rights flying</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:8bd4102f430d/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:consumer"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:aviation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:flights"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:ryanair"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:aer-lingus"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:ireland"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:rights"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:flying"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.popularmechanics.com/technology/aviation/crashes/what-really-happened-aboard-air-france-447-6611877">
    <title>Air France 447 Flight-Data Recorder Transcript - What Really Happened Aboard Air France 447 - Popular Mechanics</title>
    <dc:date>2011-12-08T15:55:06+00:00</dc:date>
    <link>http://www.popularmechanics.com/technology/aviation/crashes/what-really-happened-aboard-air-france-447-6611877</link>
    <dc:creator>jm</dc:creator><description><![CDATA[The (comp.)risks of overautomation strike again. "When trouble suddenly springs up and the computer decides that it can no longer cope—on a dark night, perhaps, in turbulence, far from land -- the humans might find themselves with a very incomplete notion of what's going on. They'll wonder: What instruments are reliable, and which can't be trusted?"]]></description>
<dc:subject>aviation crash flight flying autopilot stalls warnings alarms ui af447 risks automation</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:cc02b8859dac/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:aviation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:crash"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:flight"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:flying"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:autopilot"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:stalls"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:warnings"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:alarms"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:ui"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:af447"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:risks"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:automation"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://plus.google.com/u/0/110897184785831382163/posts/5qsNxFEaiML">
    <title>747s using VLANs to secure in-flight access to engine management systems</title>
    <dc:date>2011-11-26T09:19:29+00:00</dc:date>
    <link>https://plus.google.com/u/0/110897184785831382163/posts/5qsNxFEaiML</link>
    <dc:creator>jm</dc:creator><description><![CDATA['I was contracted to test the systems on a Boeing 747. They had added a new video system that ran over IP. They segregated this from the control systems using layer 2 VLANs. We managed to break the VLANs and access other systems and with source routing could access the Engine management systems.' (via Risks)]]></description>
<dc:subject>scary aviation flight security boeing 747 via:risks</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:84940f0c3c84/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:scary"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:aviation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:flight"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:security"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:boeing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:747"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:via:risks"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://blog.runwayfinder.com/">
    <title>RunwayFinder shut down by patent trolls</title>
    <dc:date>2010-12-16T12:22:11+00:00</dc:date>
    <link>http://blog.runwayfinder.com/</link>
    <dc:creator>jm</dc:creator><description><![CDATA[“While we appreciate your offer to shut down the website to stop future infringement, we notice that your website is still operation. And without further information from you, our only means to assess the potential damages is the observation that your website had 22,256 unique visitors in July 2010. Each visit represents a potential lost sale of our client’s patented invention at $149 per sale. This damage calculation exceeds $3.2 million per month in lost revenue.”]]></description>
<dc:subject>patents swpats patent-trolls flightprep runwayfinder aviation web law</dc:subject>
<dc:identifier>https://pinboard.in/u:jm/b:335d3fe9f697/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:patents"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:swpats"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:patent-trolls"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:flightprep"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:runwayfinder"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:aviation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:web"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:law"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://ithurtstonotbreathe.blogspot.com/2009/08/socializing-weather.html">
    <title>Socializing the Weather</title>
    <dc:date>2009-08-17T21:11:30+00:00</dc:date>
    <link>http://ithurtstonotbreathe.blogspot.com/2009/08/socializing-weather.html</link>
    <dc:creator>jm</dc:creator><description><![CDATA[so Met Eireann's crappy weather forecasts are actually just what they give out "for free"; if you pay extra, they have more accurate forecasts.  what a scam for a govt department!  Handily though, they are mandated by law to give out decent forecasts to pilots -- which are available online]]></description>
<dc:subject>eidw taf terminal-area-forecasts aviation flying pilots met-eireann weather forecasts government</dc:subject>
<dc:identifier>https://pinboard.in/u:jm/b:e56f031c0186/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:eidw"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:taf"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:terminal-area-forecasts"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:aviation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:flying"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:pilots"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:met-eireann"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:weather"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:forecasts"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:government"/>
</rdf:Bag></taxo:topics>
</item>
</rdf:RDF>