Take your pick for a simple solution ..
(a) vertical G shows a spike for my landings or, for the aces of the base .. there should be a variation in G trace between air and ground
(b) altitude trace becomes constant
(c) WOW flag
.. or use (a), (b) and (c) as a check each on the other
(d) or, if you are REALLY bored .. do it with a bit of geometry and simple speed-and-distance-back-of-a-fag-packet calculations
At the end of the day .. once the PC is programmed to flag and monitor any event, it is all done automatically in any case
I have no doubt that people with more time to waste than I have .. have found other, more elegant, ways to find the answer .. mainly this will depend on the type of data available from the box .. the more modern types of recorder (DFDR/QAR) have the capability to record many parameters. The main message is that it is pretty much a straight forward exercise ..
Surprised that you couldn't find anything on the net .. try the UK's
CAP 739 (link is on the Tech Log URL sticky) for starters
Useful to keep in mind that FOQA (or one of the other buzz terms) is not a magic thing .. it is a disciplined approach to using flight recorder data to seek improvements in procedures and SOP discipline .. not to mention the maintenance trend monitoring use of the data .. the guys and gals doing the work have to figure out just how they are going to go about it .. while keeping themselves nice along the way with respect to a bunch of regulatory, general legal, and Industrial imperatives.